skibbityboop

Not for PostgreSQL, but for MariaDB we run replicas in FreeBSD jails on a server with lots of ZFS space. The jailed Maria instances just stop every hour (so the DB flushes everything to disk), the host snapshots all of their data volumes, and then starts the jails back up. Within a minute or so they're fully caught up to the primaries again. Gives us months and months of recovery checkpoints.

It's great because it's a completely clean save from a shutdown state, so when we need a scratch copy of a database it only takes as long as cloning whatever snapshot we want (depending on how far back we need to to), then starting a scratch jail that runs from those clone filesystems. When finished, just shutdown scratch and delete the clones, it's like it never happened.

Yes, this really is an example of someone who "made it" and made a large amount of money that has allowed them to turn around and choose a simpler life. "Oh, I just moved myself and my family off to a little Greek island estate I bought and farming it (along with my existing money) is what provides for us..."

Money may not buy happiness buy money buys you all the freedom you could possibly need to do anything that fits your whimsy.

It's not like VMFS (not a cluster filesystem), for Proxmox+iSCSI you get a large LVM PV that gets sliced up into volumes for your VMs. All of your Proxmox nodes are connected to that same LVM PV and you can live migrate your VMs around all you wish, have HA policies so if a node dies its VMs start up right away on a surviving node, etc.

You lose snapshots (but can have your SAN doing snaps, of course) and a few other small things I can't recall right now, but overall it works great. Have had zero troubles.

Yes, when dementia has you terrified of, or raging at, your closest loved ones (who you don't remember at all so you think they're demons or strangers) all day every day to the point where they all can't stand you and feel terrible for wishing death would come to end your massive suffering. Beautiful moments, just beautiful.

Hanging in there with cancer? Sure, fight it and deal with the pain. Dementia? No, please end it. The two aren't even close in comparison, cancer feels easy and merciful.

Yeah, kinda have to agree. I like traefik fine but getting mTLS working with it was a serious pain and the docs for doing so were _terrible_, had to keep searching around and piecing together bits from various third party blogs. Coming from haproxy where the documentation is _so_ _much_ better and things like e.g. mTLS are vastly easier, it was not a fun experience but we did finally get traefik to work as we needed.

Anecdotal but btrfs is the only filesystem I've lost data with (and it wasn't in a RAID configuration). That combined with the btrfs tools being the most aggressively bad management utilities out there* ensure that I'm staying with ext4/xfs/zfs for now.

*Coming from the extremely well thought out and documented zfs utilities to btrfs will have you wondering wtf fairly frequently while you learn your way around.

Yeah, if your device is lost or destroyed and you rely on passkeys, you are well and truly f**ed. Your only hope is if you have recovery passwords stored in a password safe or manager. If you already have that safe or manager, than you can already very easily have 25+ character passphrases for every site you use, so what have passkeys gained you except having to be double-vigilant about having a recovery method for every login you create?

Same boat, the attempt at bot detection prevents the page from working at all for me.

Hit the same issue, but it goes fine if you just clone the repo, cd down into the cmd directory and 'go build -o doggo'.

I'm with you, I need to read up more on where timeseries could benefit, at work we have a PostgreSQL instance with around 27 billion rows in a single partitioned table, partitioned by week. Goes back to January of 2017 and just contains tons of data coming in from sensors. It's not "fast", but also not ridiculously slow to say e.g. "Give me everything for sensor 29380 in March of 2019".

I guess depends on your needs but I do think I need to investigate timeseries more to see if it'd help us.

I got a Latitude 9430 on eBay for $520. This thing is an amazing laptop and I'd put it right there with the Macs I have to work with at dayjob, as far as build quality/feel.

Anyone who has owned a Mini would probably question whether their QA even gets that far.

Maybe it depends on the McDonald's franchisee in your area, I never see free fries in the app but it's always "any size fries for $1.29" (which is still massively cheaper than their normal price).

> If you have a whole database of them, the trick is to try one code with a thousand cards

That still sounds like a crapshoot... Of those 1,000 cards, there might be 14 that have 982 as CSV, 9 that have 307, and none with 118. In other words, there's no guarantee whatsoever that any given CSV will be used in a batch of 1,000 or even 10,000 cards.

Same, in years and years of use, never a single spam message.

> yes, it adds a forwarding rule. Which skips over the rest of my firewall rules.

... which you explicitly asked it to do by using the -p option.

Works well to just spin up a python:3.11 container via Docker or Podman and do the pipx + reddit-user-to-sqlite installations, then run the utility in there. You can mount some folder as part of starting the container or copy the reddit.db file out of the container before throwing it away. Avoids any changes to your real system at all.

1. Install regular old Docker

2. Type 'docker swarm init'

3. There is no 3, you're literally finished and now have a full-on Swarm node w/ all features.

Great question, and yes, some of the better devices implement a small buffer so may be able to keep a day or even two in memory while they're out of cell coverage. If you activate the SIM you might get a small data dump.

GPS doesn't need a SIM, and indeed the devices will have a fix all the time whether activated or not. They do require cell service to send their updates anywhere. They're all simple GPS receivers, not transmitters, thus require an active SIM.

> Is the sky-link GPS device still sending location data back to a Sky Link server?

As someone who used to work in that industry, no, it's not sending location data. You don't activate the SIM until you have someone who is going to pay for the service, otherwise you're losing money for no reason.

We'd get that question often though, someone activating a device hoping they'd be able to see everywhere it was for the last month.

Heh, can you imagine having to take over the systems managed by that poster? You'd have to rip and replace everything.

What about it isn't idempotent for you? Are you falling into the anti-pattern of using shell/command all over the place instead of real modules?

We have playbooks installing and managing our databases, web servers, VoIP PBX, DNS servers, backend services, and on and on. All completely idempotent and safe to run at any time against any host. No special effort whatsoever was required to make that safe to do.

My friends and I all own/owned it legitimately (we had LAN parties nearly every weekend), but over time we'd lose the key. Just entering all 3s has always worked and it accepts it as a valid key.

We run it (Docker Swarm) extensively inhouse at $dayjob, it runs loads of core services that are critical to operations. It's never given us any grief and is very easy to manage and maintain.

If the complexity ever gets to the point that k8s is justified we'll move there, but you can get a lot of work done with the much simpler Swarm.

Have you finally stopped buying Intel? Current Ryzens are a much better CPU anyhow, just dump Intel and be happy with your ECC and everything else.

Cool blog post, thx for sharing. Typo in it: "So I road my motorcycle into the jungle"

Here here! The docs don't really make it clear what Airflow is for someone who hasn't already used or been exposed to it. Is it a job scheduler like Rundeck? Something else?

Needing VMs to perform well, comparably to KVM/Xen, would be a blocker for going BSD.

Jails are awesome but not containers you're blocked there as well (if you need containers and the tooling around them).

> in the first half of 2021

Well, you've panicked people who are/were moving forward with CentOS 6/7 to 8, and not on RHEL because no budget. "Don't worry, sometime in the next 6 months there might be useful info for you, or there might not".

People aren't going to stick around waiting for that information. You've pulled the rug out from under us and we need to plan sooner rather than later. RHEL isn't do-able due to cost, CentOS isn't do-able because you've just killed it, so away we have to go.

However, if you're in the SMB space and run CentOS as production because money is tight but you wanted a stable LTS distro and have never needed any technical support, this move has just yanked the rug out from under you and there appear to be no provisions in the pipeline to change that.

Your only option is to migrate away from RHEL/CentOS, period. It's likely that Red Hat doesn't care much about us smaller orgs with only 100-200 servers/VMs though. Sad day.