Hi Stephen,
I do apologize for the accidental top-post - thank you for pointing it out!
On Fri, May 19, 2023 at 4:13 PM Stephen Frost wrote:
> Perhaps an argument can be made that replication slots should be
> optional for pg_basebackup to include or not (and similarily for other
> PG backup too
Greetings,
Please don't top-post on these lists.
* Kristjan Mustkivi (sonicmon...@gmail.com) wrote:
> Thank you very much for the feedback and a reference! I was under the
> impression that pg_basebackup does everything
> pg_start_backup/pg_stop_backup but with a more user-friendly manner
> and a
Hi Stephen,
Thank you very much for the feedback and a reference! I was under the
impression that pg_basebackup does everything
pg_start_backup/pg_stop_backup but with a more user-friendly manner
and additional steps. But they are then functionally different. For my
particular case the pg_start_ba
Greetings,
* PG Doc comments form (nore...@postgresql.org) wrote:
> It would be good to point out on the pg_basebackup documentation that it
> behaves differently from
>
> SELECT * FROM pg_start_backup('label', true, false);
> cp -a xxx yyy
> SELECT * FROM pg_stop_backup(false, true);
... that's
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/11/app-pgbasebackup.html
Description:
Hello!
It would be good to point out on the pg_basebackup documentation that it
behaves differently from
SELECT * FROM pg_start_backup('label', true, f
