Re: Hot Backup with rsync fails at pg_clog if under load
| От | Florian Pflug |
|---|---|
| Тема | Re: Hot Backup with rsync fails at pg_clog if under load |
| Дата | |
| Msg-id | 647BE58F-ED68-497C-8122-237E6327C075@phlo.org обсуждение исходный текст |
| Ответ на | Re: Hot Backup with rsync fails at pg_clog if under load (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>) |
| Ответы |
Re: Hot Backup with rsync fails at pg_clog if under load
|
| Список | pgsql-hackers |
On Sep23, 2011, at 10:41 , Heikki Linnakangas wrote: > On 23.09.2011 11:02, Linas Virbalas wrote: >> On 9/22/11 6:59 PM, "Euler Taveira de Oliveira"<euler@timbira.com> wrote: >> >>>> If needed, I could do that, if I had the exact procedure... Currently, >>>> during the start of the backup I take the following information: >>>> >>> Just show us the output of pg_start_backup and part of the standby log with >>> the following message 'redo starts at' and the subsequent messages up to the >>> failure. >> >> Unfortunately, it's impossible, because the error message "Could not read >> from file "pg_clog/0001" at offset 32768: Success" is shown (and startup >> aborted) before the turn for "redo starts at" message arrives. > > It looks to me that pg_clog/0001 exists, but it shorter than recovery expects. Which shouldn't happen, of course, becausethe start-backup checkpoint should flush all the clog that's needed by recovery to disk before the backup procedurebegins to them. Yeah. What confuses me though is that we fail while trying to read from the clog. When do we do that during normal (non-standby)recovery? One other possibility would be that the problem is somehow triggered by vacuum running while the start-backup checkpointis commencing. That'd explain why the problem goes away with immediate checkpoints, because those make the windowsmach smaller. But I haven't got a concrete theory of whats happening.. best regards, Florian Pflug
В списке pgsql-hackers по дате отправления: