101–110 of 125 posts
This might help people when looking for an alternative. https://wheretohostmy.app/?tech=%5B%22postgresql%22%5D It's a side project I'm currently building so hearing some feedback is highly appreciated.
Fly.io also seems to be missing. Great for Elixir and Rails. Pretty great Heroku replacement
I switched to DigitalOcean and it's been a delight. $15/month for a managed Postgres is a good deal, and I am really tired of the hellscape that has become AWS configuration even for the most simplest things. Isn't the whole point of the cloud is simplicity?
The main thing I'm looking for in managed PostgreSQL isn't "installation" -- that's easy -- what I need is not to have to spend weeks of configuring and testing and drilling, to be reasonably confident that I won't lose customer data.
I see DigitalOcean does PG standby servers, and daily backups, but I'm unclear on whether they're doing separate, say, WAL-based backups.
The couple mentions I saw of "PITR" seemed to conflate that with the daily backups.
There's a partial description of the UI, but it's still unclear: https://docs.digitalocean.com/products/databases/postgresql/...
> In the Create a new cluster from a backup window that opens, choose whether you want to restore to the latest transaction available or choose a point in time,
What's the "latest transaction available"?
(Is it to moments before someone ripped the cables out of the storage server? Or is it the most recent daily backup, which might've been 23 hours ago?)
> By default, the name is the original databases’ name appended with the date of the backup and the word “backup”, like originalname-aug-13-backup.
I don't want to be trying urgently to recover the businesses of myself and my customers, and find myself asking design questions akin to "Why isn't this a UTC ISO date/timestamp?" but more like "Why are the backups done in such a way that they can't be restored for this ordinary failure scenario that just happened?"
I don't see any technical reason that a cloud provider can't give enterprise DBA confidence at kitchen table startup rates, but I'd feel silly for assuming that they do.
Earlier quoted context omitted.
Fly.io also seems to be missing. Great for Elixir and Rails. Pretty great Heroku replacement
Fly.io is covered. Here's the list of all hosting services currently supported: https://wheretohostmy.app/services
Earlier quoted context omitted.
Fly.io is covered. Here's the list of all hosting services currently supported: https://wheretohostmy.app/services
We're not really a managed Postgres service, for what it's worth (we like Supabase a lot for hardcore managed Postgres).
Earlier quoted context omitted.
From what the migration doc says, it will only support pgdump migration. Meaning it will require downtime, or at least write downtime. Create backup using pgdump, restore the dump to new database. While making sure no changes to the old db before switch over.
Ouch that will make migrating anything over a few hundred gigs almost impossible. Our postgres db is about 2TB and pgdump stopped being viable a long time ago.
Earlier quoted context omitted.
What has gotten more complicated that used to be simpler in AWS?
I started with AWS pretty early. Networking was drop dead simple. Basically I think all my instances got an 10.x.x.x IP address. You had a basic firewall (security groups nowadays) but that was it. Let's say you had another account for a separate project or a client with another account. You could literally connect to their instance via private IP. All your own resources and all theirs were in this same 10.x.x.x addr…
The Aiven company they have partnered with's website seems to be down. Bad omen.
Earlier quoted context omitted.
Also Vultr https://www.vultr.com/products/managed-databases/postgresql/
Related: https://news.ycombinator.com/item?id=39836495
https://www.vultr.com/news/a-note-about-vultrs-terms-of-serv...
Earlier quoted context omitted.
> and it's not easy to guard your users' privacy against them Source? > Smaller providers (and also local in the case of 84codes) are preferred AWS have a reputation and stability to keep because half of the internet, governments, banks, etc. rely on them. If a small provider makes a mistake, or goes bankrupt due to unforseen circumstances, you're left holding the bag on your own.
If AWS goes down, and it does, you're still left holding the bag, because no one customer is important enough for them to actually support. You can leave sad voicemails for your customer account representative, and pretty much nothing else. The idea of AWS as some kind of bag-holding partner is risible. They're a machine that helps convert capex to opex. Any systems services they may offer along the way are purely se…
Rarely. And never if you've setup your environment across multiple regions.