public inbox for [email protected]  

help / color / mirror / Atom feed

From: David G. Johnston <[email protected]>
To: Dmitry O Litvintsev <[email protected]>
Cc: pgsql-generallists.postgresql.org <[email protected]>
Subject: Re: Confusing error message in 15.6
Date: Tue, 21 May 2024 16:50:14 -0700
Message-ID: <CAKFQuwZDZR4yf1t5hzVrE_D-0Lv-8W-8f3VFkcrXe4vChWUQNw@mail.gmail.com> (raw)
In-Reply-To: <CAKFQuwaBvMX671=AUsuukkeU2hv0iSSA9=ixDXzBWM8WLCtRwg@mail.gmail.com>
References: <SA1PR09MB731160449C3C97197555F1F3B9EA2@SA1PR09MB7311.namprd09.prod.outlook.com>
	<CAKFQuwaBvMX671=AUsuukkeU2hv0iSSA9=ixDXzBWM8WLCtRwg@mail.gmail.com>

On Tuesday, May 21, 2024, David G. Johnston <[email protected]>
wrote:
>
> On Tue, May 21, 2024, 17:29 Dmitry O Litvintsev <[email protected]> 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’s only the connection, not a transaction.


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

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

David J.

view thread (4+ 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], [email protected], [email protected]
  Subject: Re: Confusing error message in 15.6
  In-Reply-To: <CAKFQuwZDZR4yf1t5hzVrE_D-0Lv-8W-8f3VFkcrXe4vChWUQNw@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