From: PG Doc comments form <noreply@postgresql.org>
To: pgsql-docs@lists.postgresql.org
Cc: sonicmonkey@gmail.com
Subject: pg_basebackup application does not dump all database objects
Date: Tue, 16 May 2023 11:49:23 +0000
Message-ID: <168423776321.714.17805484409630880522@wrigleys.postgresql.org> (raw)
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, false);
cp -a xxx yyy
SELECT * FROM pg_stop_backup(false, true);
method. One thing discovered was that the latter retains replication slot
information on the clone while pg_basebackup discards all replication slot
information. Not sure if it is a feature or a bug (replication slots
retention is a good thing).
And perhaps there are more such subtle differences?
With best regards,
Kristjan Mustkivi
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: pgsql-docs@postgresql.org
Cc: noreply@postgresql.org, pgsql-docs@lists.postgresql.org, sonicmonkey@gmail.com
Subject: Re: pg_basebackup application does not dump all database objects
In-Reply-To: <168423776321.714.17805484409630880522@wrigleys.postgresql.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox