| From: | PG Doc comments form <noreply(at)postgresql(dot)org> |
|---|---|
| To: | pgsql-docs(at)lists(dot)postgresql(dot)org |
| Cc: | sonicmonkey(at)gmail(dot)com |
| Subject: | pg_basebackup application does not dump all database objects |
| Date: | 2023-05-16 11:49:23 |
| Message-ID: | 168423776321.714.17805484409630880522@wrigleys.postgresql.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2023-05-16 14:14:45 | Re: pg_basebackup application does not dump all database objects |
| Previous Message | Daniel Gustafsson | 2023-05-15 12:35:36 | Re: tables on pgbench man page look garbled |