| From: | Sébastien Lardière <slardiere(at)hi-media(dot)com> |
|---|---|
| To: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
| Cc: | Martin Pihlak <martin(dot)pihlak(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org, skytools-users(at)pgfoundry(dot)org |
| Subject: | Re: [Skytools-users] WAL Shipping + checkpoint |
| Date: | 2009-08-31 08:16:33 |
| Message-ID: | 4A9B86E1.5000109@hi-media.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 28/08/2009 18:14, Simon Riggs wrote:
> On Fri, 2009-08-28 at 17:54 +0200, Sébastien Lardière wrote:
>
>> Since this moment, the slave didn't make any checkpoint.
>>
>> Now, we know why. Thanks a lot !
>>
>> But how can i fix it ?
>>
> Current issue: Rebuild standby from base backup.
>
> Cause: Locate the bug in the Index AM that causes it.
>
> Symptom: Currently index AMs don't detect situation that index is
> corrupt so they keep trying to recover the index for ever, even though
> attempting to do so permanently prevents restartpoints. I would also
> like them to have a mechanism for marking index corrupt and then
> auto-rebuild them following recovery.
>
Thanks, I make a restore backup on the slave this morning, and It works !
Thanks a lot,
--
Sébastien Lardière
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daniel Verite | 2009-08-31 09:19:30 | Re: Problem libpython2.3.so.1.0 |
| Previous Message | nesfree | 2009-08-31 08:01:05 | Re: Problem libpython2.3.so.1.0 |