Re: Re: [COMMITTERS] pgsql: Make standby server continuously retry restoring the next WAL
| От | Heikki Linnakangas |
|---|---|
| Тема | Re: Re: [COMMITTERS] pgsql: Make standby server continuously retry restoring the next WAL |
| Дата | |
| Msg-id | 4B73F678.8070109@enterprisedb.com обсуждение исходный текст |
| Ответ на | Re: Re: [COMMITTERS] pgsql: Make standby server continuously retry restoring the next WAL (Simon Riggs <simon@2ndQuadrant.com>) |
| Ответы |
Re: Re: [COMMITTERS] pgsql: Make standby server
continuously retry restoring the next WAL
|
| Список | pgsql-hackers |
Simon Riggs wrote: > On Wed, 2010-02-10 at 09:32 +0200, Heikki Linnakangas wrote: >> Hmm, so after running restore_command, check the file size and if it's >> too short, treat it the same as if restore_command returned non-zero? >> And it will be retried on the next iteration. Works for me, though OTOH >> it will then fail to complain about a genuinely WAL file that's >> truncated for some reason. I guess there's no way around that, even if >> you have a script as restore_command that does the file size check, it >> will have the same problem. > > Are we trying to re-invent pg_standby here? That's not the goal, but we seem to need some of the same functionality in the backend now. -- Heikki Linnakangas EnterpriseDB http://www.enterprisedb.com
В списке pgsql-hackers по дате отправления: