On Wed, Mar 12, 2025 at 4:16 PM Paul Foerster <paul.foerster@xxxxxxxxx> wrote:
Hi Ron,
> On 12 Mar 2025, at 17:59, Ron Johnson <ronljohnsonjr@xxxxxxxxx> wrote:
>
> Developers making DDL changes on production databases?
Of course not. But I can't block developer databases. That'd make a few hundred developers happy.
> Or are there prod and dev databases on the same instance? If so, then know that you don't have to logically replicate the whole instance.
Also of course not. There is development, pre-production and production.
Outages on development databases make a few hundred developers happy, while outages of production databases are appreciated by up to almost 40K users, depending on the application.
Anyway, this is our concern. In our environment, logical replication is impossible for development databases, hard for pre-production because of automatic deployments and only possible on production databases.
Anyway, this is going off-topic now.
No, I think it's 100% on point: logically replicate the Prod databases, while pg_dump/pg_restore of the dev and pre-prod databases happen on weekends.
Death to <Redacted>, and butter sauce.
Don't boil me, I'm still alive.
<Redacted> lobster!
