Just don't try to build it from source haha. Compiling Postgres 18 with the PostGIS extension has been such a PITA because the topology component won't configure to not use the system /usr/bin/postgres and has given me a lot of grief. Finally got it fixed I think though.

Without disagreeing:

Sometimes it is nice to simplify the conversation with non-tech management. Oh, you want HA / DR / etc? We click a button and you get it (multi-AZ). Clicking the button doubles your DB costs from x to y. Please choose.

Then you have one less repeating conversation and someone to blame.

I've had to set up postgres manually ( before docker TBF) and it's best described as suffering.

Things will go wrong. And it's all your fault. You can't just blame AWS.

Also are we changing the definition of self hosting. Self hosting on Digital Ocean ?!

Disk read write performance is also orders of magnitude better/cheaper/faster.

What's the SOTA for on-prem Postgres, in terms of point-in-time-recovery? are there any well-tested tools for it?

One of the things that made me think twice for self hosting postgres is securing the OS I host PG on. Any recommendation where to start for that?

People really love jumping through hoops to avoid spending five dollars.

I moved from AWS RDS to ScaleWay RDS, had the same effect on cost

Huh? Maybe I missed something, but...why should self-hosting a database server be hard or scary? Sure, you are then responsible for security backups, etc...but that's not really different in the cloud - if anything, the cloud makes it more complicated.

Pros self-host their DB's