Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tsT2J-002Je0-16 for pgsql-general@arkaria.postgresql.org; Wed, 12 Mar 2025 20:50:43 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1tsT2H-00DRRA-QI for pgsql-general@arkaria.postgresql.org; Wed, 12 Mar 2025 20:50:41 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tsT2H-00DRR0-F8 for pgsql-general@lists.postgresql.org; Wed, 12 Mar 2025 20:50:41 +0000 Received: from mail-oi1-x229.google.com ([2607:f8b0:4864:20::229]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1tsT2F-002UZu-0y for pgsql-general@postgresql.org; Wed, 12 Mar 2025 20:50:40 +0000 Received: by mail-oi1-x229.google.com with SMTP id 5614622812f47-3fa6c54cc1aso180120b6e.1 for ; Wed, 12 Mar 2025 13:50:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1741812638; x=1742417438; darn=postgresql.org; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=m58vB+P5Nocrz+ivvsBQgGFhgsqp1j0VB32Q9ei91TY=; b=NoVIVqKp1USdogeX7/GzdP/Zs9jar+sgUEdGv92fduf+2P12s/EeGSdIv/Pc8cTZ9u YrglWYTfmPdua8yrdKFBKwu7Ez+PjeF84VBn3NjYzkkX6pSaB9rSggzBinluoTzXq+2L e2eJvXJL/qyH2/QC1JXzNO6jRxFTkIz5Bi+8fe1zLIIi/vJZ/Xj6gHoTYD5qNpiROP4b 2mwureeapci3b1IR6uMQZpC2i145tYkJp1lm+tKyVFazG/EjjzSoVdgjGlWnYI1jbpC/ 6lsNNJKGVz9qv0absJ4O5k/pCYVO1DlmYfxK9ItnWCFnkmw+RGs4JMsdtFR9QJeou68X FgqA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1741812638; x=1742417438; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=m58vB+P5Nocrz+ivvsBQgGFhgsqp1j0VB32Q9ei91TY=; b=DsQIHEBu1/RScunH53yDjz90KxKcDbTvGbcAUSCuOIOcKB2lXiv0SrT5D0b89p248H za7L3VRn57oCjQbUTGzCG68cRsUJ2acRZS4qZ4UzqqKwdF2GuzpDOVgtFY5aMMcPiG6r ChI3e8LvQOnIwG1ShGC9t3f/fuvePkrUetB1oaXQG6xr3seCmh8NR91lRAXBzNVz0JeE oRbI4WeU0iwGydnf7gukpJiqvL1JRnl534nu/9wIjbH2qLKOqsNClLW7FcstuG9qQ691 /7QJLFb1oDgXkULjsmwQSQ9LSaWJHJUbbApi4uCHNf1ZDhB5GPgdMYtahgVQcg9t7lRf xgdA== X-Gm-Message-State: AOJu0YwdTaENRduA/6qfnQbLUcyADzI7FMxCdNpA6I4BMHgwgQS4bWms WPbUqL5xL4uwYy1TD4nb/fj9BR1ApOtjwPWIYYQMFcFJtdt8+JiSiRRrB8KQsOK5mG77yzBYhSB /3aMIOKhs2gkODZx7mD1zBZQGjEO+jg== X-Gm-Gg: ASbGnctdCi1CsU4FxMV1RIJhl+7L8ElRoGz/uJDPHgPepHjdw7FVqgeg3mWjsxICncS qymdHItmxNuURtEr+JPMEuQ6pSWkDCpcJPX+CH8/tsIrdN6aIvCc/I0lgwoFs2tNaj7nHiw9Yef qEuTCEGrjcgz2q6t8JK4O7CcJYRYGNuzRMutFi9qb10Vi01V9JzP1dNR3JXpC8 X-Google-Smtp-Source: AGHT+IG3K39gX3D2vF6ArHqPs6HocmNhBdjl2vWZul0w80duAuIZT4etk++ahKLiM33t4rkb+OqUzb6mJH0MYZQs53I= X-Received: by 2002:a05:6808:10a:b0:3f6:a1f8:ce3 with SMTP id 5614622812f47-3f6a1f80e11mr7686568b6e.14.1741812638513; Wed, 12 Mar 2025 13:50:38 -0700 (PDT) MIME-Version: 1.0 References: <6E6059F6-E5A1-4A8D-8A5E-A41B921BBE67@gmail.com> <1DA96F05-D9BF-4D68-80D3-3F3F99691C8D@gmail.com> <7FC835F0-FE59-45B3-8866-83E8549191D7@thebuild.com> <843A9EE2-BAA1-4C4B-8DE6-74ECAFB113B4@gmail.com> In-Reply-To: <843A9EE2-BAA1-4C4B-8DE6-74ECAFB113B4@gmail.com> From: Ron Johnson Date: Wed, 12 Mar 2025 16:50:25 -0400 X-Gm-Features: AQ5f1Jq6bofQDwKr9y058cDHdVC4Tz5rmtKyXz1YFyeGJxF7aPgulERdff6IA2Y Message-ID: Subject: Re: Moving from Linux to Linux? To: pgsql-general Content-Type: multipart/alternative; boundary="00000000000095845806302b5be7" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --00000000000095845806302b5be7 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Wed, Mar 12, 2025 at 4:16=E2=80=AFPM Paul Foerster wrote: > Hi Ron, > > > On 12 Mar 2025, at 17:59, Ron Johnson 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. --=20 Death to , and butter sauce. Don't boil me, I'm still alive. lobster! --00000000000095845806302b5be7 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Wed, Mar 12, 2025 at 4:16=E2=80=AFPM P= aul Foerster <paul.foerster@g= mail.com> wrote:
Hi Ron,

> On 12 Mar 2025, at 17:59, Ron Johnson <ronljohnsonjr@gmail.com> 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?=C2=A0 If so,= then know that you don't have to logically replicate the whole instanc= e.

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 imp= ossible for development databases, hard for pre-production because of autom= atic 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, w= hile pg_dump/pg_restore of the dev and pre-prod databases happen on weekend= s.

--
Death to= <Redacted>, and butter sauce.
Don't boil me, I'm still a= live.
<Redacted> lobster!
<= /div> --00000000000095845806302b5be7--