public inbox for [email protected]
help / color / mirror / Atom feedFrom: Ron Johnson <[email protected]>
To: pgsql-general <[email protected]>
Subject: Re: Moving from Linux to Linux?
Date: Wed, 12 Mar 2025 16:50:25 -0400
Message-ID: <CANzqJaAK7yTv0=DVAjMGwqZBhhEogLL=h=t=qudeAgqPXoNLgg@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
<[email protected]>
<CANzqJaCj4uf-7_ErTP9eHn_rxomRHMDbKAm7M15eAWiRbxZgmA@mail.gmail.com>
<[email protected]>
<[email protected]>
<[email protected]>
<CANzqJaCfAc-5v==VHEEizejAbg3OXfjN25Psz2sHRad_OQeajg@mail.gmail.com>
<[email protected]>
On Wed, Mar 12, 2025 at 4:16 PM Paul Foerster <[email protected]>
wrote:
> Hi Ron,
>
> > On 12 Mar 2025, at 17:59, Ron Johnson <[email protected]> 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!
view thread (18+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected]
Subject: Re: Moving from Linux to Linux?
In-Reply-To: <CANzqJaAK7yTv0=DVAjMGwqZBhhEogLL=h=t=qudeAgqPXoNLgg@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox