| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Dmitry O Litvintsev <litvinse(at)fnal(dot)gov> |
| Cc: | "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Confusing error message in 15.6 |
| Date: | 2024-05-21 23:50:14 |
| Message-ID: | CAKFQuwZDZR4yf1t5hzVrE_D-0Lv-8W-8f3VFkcrXe4vChWUQNw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Tuesday, May 21, 2024, David G. Johnston <david(dot)g(dot)johnston(at)gmail(dot)com>
wrote:
>
> On Tue, May 21, 2024, 17:29 Dmitry O Litvintsev <litvinse(at)fnal(dot)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’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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dmitry O Litvintsev | 2024-05-21 23:58:42 | Re: Confusing error message in 15.6 |
| Previous Message | David G. Johnston | 2024-05-21 23:42:37 | Re: Confusing error message in 15.6 |