MIME-Version: 1.0
References: <CAD=40Z3Rvbx46SxYBBdLvgSObXCP+Firszz++rDTXmGX795D2Q@mail.gmail.com>
 <6c498f0e-64f9-449a-9b90-5cd72d00e2ef@aklaver.com> <CAD=40Z1wJ7mBej9=Yqfo_1m-eOV61E=s6yDjZSaTBESbGunBUA@mail.gmail.com>
 <2a7d96ac-83a7-4ddc-a3ce-9c637f2c1c76@aklaver.com> <CAD=40Z3prwhLAedetocCu3jFvHSBP44V6O9d6CXjvzLTw7eOUQ@mail.gmail.com>
 <CANzqJaACBw1=jCAxGwSeu7dh4UfD2KePcNqSOC3=WwzXrg0skQ@mail.gmail.com>
 <CAD=40Z3k2dgVidM3oYuMWsauHyKF9v-0i4nOfMXd917PtNiO_g@mail.gmail.com>
 <1FBD217B-06FE-48CF-AA58-F7ADEDA5ADD2@thebuild.com> <CANzqJaANutDZy-bRCC1Sf0X7=LtF2HHMBfk73_MmVyXBReL4=w@mail.gmail.com>
 <60D0A828-451D-48B1-8A47-B246806A03E5@thebuild.com>
In-Reply-To: <60D0A828-451D-48B1-8A47-B246806A03E5@thebuild.com>
From: Ron Johnson <ronljohnsonjr@gmail.com>
Date: Sun, 24 Nov 2024 16:00:08 -0500
Message-ID: <CANzqJaCbagpPpt6mhjA1UDCJ6xpHV-SWim6vOCWKcZjRjuSm=g@mail.gmail.com>
Subject: Re: Questions on Upgrading PostgreSQL from 15.0 to 15.9 and Setting
 Up Streaming Replication
To: pgsql-general <pgsql-general@postgresql.org>
Content-Type: multipart/alternative; boundary="0000000000005671420627aee71c"
Archived-At: <https://www.postgresql.org/message-id/CANzqJaCbagpPpt6mhjA1UDCJ6xpHV-SWim6vOCWKcZjRjuSm%3Dg%40mail.gmail.com>
Precedence: bulk

--0000000000005671420627aee71c
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Sun, Nov 24, 2024 at 2:55=E2=80=AFPM Christophe Pettus <xof@thebuild.com=
> wrote:

> > On Nov 24, 2024, at 09:15, Ron Johnson <ronljohnsonjr@gmail.com> wrote:
> >
> > Doesn't the existence of a replication slot force PG to retain WAL file=
s
> when replication is broken?
>
> It does.  I don't recall if the OP said that they were using a persistent
> replication slot or not; it's not as common with binary replication as wi=
th
> logical replication.
>

Really? I wonder why people fight with configuring max_wal_size and
wal_keep_size, when replication slots do all the work for you.

--=20
Death to <Redacted>, and butter sauce.
Don't boil me, I'm still alive.
<Redacted> lobster!

--0000000000005671420627aee71c
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">On Sun, Nov 24, 2024 at 2:55=E2=80=AFPM C=
hristophe Pettus &lt;<a href=3D"mailto:xof@thebuild.com">xof@thebuild.com</=
a>&gt; wrote:</div><div class=3D"gmail_quote"><blockquote class=3D"gmail_qu=
ote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,20=
4);padding-left:1ex">&gt; On Nov 24, 2024, at 09:15, Ron Johnson &lt;<a hre=
f=3D"mailto:ronljohnsonjr@gmail.com" target=3D"_blank">ronljohnsonjr@gmail.=
com</a>&gt; wrote:<br>
&gt; <br>
&gt; Doesn&#39;t the existence of a replication slot force PG to retain WAL=
 files when replication is broken?<br>
<br>
It does.=C2=A0 I don&#39;t recall if the OP said that they were using a per=
sistent replication slot or not; it&#39;s not as common with binary replica=
tion as with logical replication.<br>
</blockquote></div><div><br clear=3D"all"></div><div>Really? I wonder why p=
eople fight with configuring max_wal_size and wal_keep_size, when replicati=
on slots do all the work for you.</div><div><br></div><span class=3D"gmail_=
signature_prefix">-- </span><br><div dir=3D"ltr" class=3D"gmail_signature">=
<div dir=3D"ltr">Death to &lt;Redacted&gt;, and butter sauce.<div>Don&#39;t=
 boil me, I&#39;m still alive.<br><div><div>&lt;Redacted&gt; lobster!</div>=
</div></div></div></div></div>

--0000000000005671420627aee71c--