MIME-Version: 1.0
In-Reply-To: <CAKFQuwaBvMX671=AUsuukkeU2hv0iSSA9=ixDXzBWM8WLCtRwg@mail.gmail.com>
References: <SA1PR09MB731160449C3C97197555F1F3B9EA2@SA1PR09MB7311.namprd09.prod.outlook.com>
 <CAKFQuwaBvMX671=AUsuukkeU2hv0iSSA9=ixDXzBWM8WLCtRwg@mail.gmail.com>
From: "David G. Johnston" <david.g.johnston@gmail.com>
Date: Tue, 21 May 2024 16:50:14 -0700
Message-ID: <CAKFQuwZDZR4yf1t5hzVrE_D-0Lv-8W-8f3VFkcrXe4vChWUQNw@mail.gmail.com>
Subject: Re: Confusing error message in 15.6
To: Dmitry O Litvintsev <litvinse@fnal.gov>
Cc: "pgsql-generallists.postgresql.org" <pgsql-general@lists.postgresql.org>
Content-Type: multipart/alternative; boundary="000000000000befe410618ff7ab6"
Archived-At: <https://www.postgresql.org/message-id/CAKFQuwZDZR4yf1t5hzVrE_D-0Lv-8W-8f3VFkcrXe4vChWUQNw%40mail.gmail.com>
Precedence: bulk

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

On Tuesday, May 21, 2024, David G. Johnston <david.g.johnston@gmail.com>
wrote:
>
> On Tue, May 21, 2024, 17:29 Dmitry O Litvintsev <litvinse@fnal.gov> wrote=
:
>
>>
>> This is not just amusing, it is breaking my backup script after update
>> from 11 to 15 (and change from pg_{start,stop}_backup to
>> pg_backup_{start_stop})
>>
>
>
> Yep, nowadays you must keep the transaction where you issued backup start
> open until you issue backup end.  Using -c isn't going to cut it.
>
>
Right, it=E2=80=99s only the connection, not a transaction.


https://www.postgresql.org/docs/current/continuous-archiving.html#BACKUP-LO=
WLEVEL-BASE-BACKUP

And this is why the name changed, because the behavior is so different.

David J.

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

On Tuesday, May 21, 2024, David G. Johnston &lt;<a href=3D"mailto:david.g.j=
ohnston@gmail.com">david.g.johnston@gmail.com</a>&gt; wrote:<blockquote cla=
ss=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;pa=
dding-left:1ex"><div dir=3D"auto"><div><div class=3D"gmail_quote"><div dir=
=3D"ltr" class=3D"gmail_attr">On Tue, May 21, 2024, 17:29 Dmitry O Litvints=
ev &lt;<a href=3D"mailto:litvinse@fnal.gov" target=3D"_blank">litvinse@fnal=
.gov</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"mar=
gin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>This is not=
 just amusing, it is breaking my backup script after update from 11 to 15 (=
and change from pg_{start,stop}_backup to pg_backup_{start_stop})<br></bloc=
kquote></div></div><div dir=3D"auto"><br></div><div dir=3D"auto"><br></div>=
<div dir=3D"auto">Yep, nowadays you must keep the transaction where you iss=
ued backup start open until you issue backup end.=C2=A0 Using -c isn&#39;t =
going to cut it.</div><div dir=3D"auto"><br></div></div></blockquote><div><=
br></div><div>Right, it=E2=80=99s only the connection, not a transaction.</=
div><div><br></div><div>=C2=A0<a href=3D"https://www.postgresql.org/docs/cu=
rrent/continuous-archiving.html#BACKUP-LOWLEVEL-BASE-BACKUP">https://www.po=
stgresql.org/docs/current/continuous-archiving.html#BACKUP-LOWLEVEL-BASE-BA=
CKUP</a></div><div><br></div><div>And this is why the name changed, because=
 the behavior is so different.</div><div><br></div><div>David J.</div><div>=
<br></div>

--000000000000befe410618ff7ab6--