Re: 9.2.3 crashes during archive recovery
От | Ants Aasma |
---|---|
Тема | Re: 9.2.3 crashes during archive recovery |
Дата | |
Msg-id | CA+CSw_uRWL8WbXKps6a6u-nm2zCp2NtNwEGX6xk+r7u6GOJY0A@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: 9.2.3 crashes during archive recovery (Heikki Linnakangas <hlinnakangas@vmware.com>) |
Список | pgsql-hackers |
<p dir="ltr"><br /> On Feb 13, 2013 10:29 PM, "Heikki Linnakangas" <<a href="mailto:hlinnakangas@vmware.com">hlinnakangas@vmware.com</a>>wrote:<br /> > Hmm, I just realized a little problemwith that approach. If you take a base backup using an atomic filesystem backup from a running server, and start archiverecovery from that, that's essentially the same thing as Kyotaro's test case.<p dir="ltr">Coincidentally I was wonderingabout the same thing when I was reviewing our slave provisioning procedures. There didn't seem to be any communicationchannel from pg_stop_backup for the slave to know when it was safe to allow connections.<p dir="ltr">Maybe thereshould be some mechanism akin to backup label to communicate the minimum recovery point? When the min recovery pointfile exists the value inside it is used, when the recovery point is reached the file is removed. pg_basebackup wouldjust append the file to the archive. Custom backup procedures could also use it to communicate the necessary WAL location.<pdir="ltr">--<br /> Ants Aasma<br />
В списке pgsql-hackers по дате отправления: