Re: WIP/PoC for parallel backup
| От | Asif Rehman |
|---|---|
| Тема | Re: WIP/PoC for parallel backup |
| Дата | |
| Msg-id | CADM=JehkorfTUNSQmVSd9Cn3EBEcxe3SoiY1jFtb8A8k2xnmWg@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: WIP/PoC for parallel backup (Rajkumar Raghuwanshi <rajkumar.raghuwanshi@enterprisedb.com>) |
| Ответы |
Re: WIP/PoC for parallel backup
|
| Список | pgsql-hackers |
On Mon, Mar 16, 2020 at 11:08 AM Rajkumar Raghuwanshi <rajkumar.raghuwanshi@enterprisedb.com> wrote:
Thanks for the patches.I have verified reported issues with new patches, issues are fixed now.I got another observation where If a new slot name given without -C option, it leads to server crash error.[edb@localhost bin]$ ./pg_basebackup -p 5432 -j 4 -D /tmp/bkp --slot test_bkp_slotpg_basebackup: error: could not send replication command "START_REPLICATION": ERROR: replication slot "test_bkp_slot" does not existpg_basebackup: error: could not list backup files: server closed the connection unexpectedlyThis probably means the server terminated abnormallybefore or while processing the request.pg_basebackup: removing data directory "/tmp/bkp"
It seems to be an expected behavior. The START_BACKUP command has been executed, and
pg_basebackup tries to start a WAL streaming process with a non-existent slot, which results in
an error. So the backup is aborted while terminating all other processes.
--
Asif Rehman
В списке pgsql-hackers по дате отправления: