| From: | Maciek Sakrejda <m(dot)sakrejda(at)gmail(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)2ndquadrant(dot)com> |
| Cc: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: BUG #10432: failed to re-find parent key in index |
| Date: | 2014-05-29 17:44:37 |
| Message-ID: | CAOtHd0B8n_K13ajd_V7zewDG5m5Q+nfQGBh0Ht8486-ttnyKtw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Thu, May 29, 2014 at 10:19 AM, Andres Freund <andres(at)2ndquadrant(dot)com>
wrote:
> The WAL should be the same everywhere... But what I was wondering about
> was less about the xlogdump but more about the lack of a message that
> tells us the record that triggered the error.
>
No idea. I'm new to pg_xlogdump, but I did get output if I went further
back, so I'm pretty sure I was using it correctly.
> So, this is quite possibly just a 'delayed' consequence from the earlier
> bugs.
>
Yeah, makes sense. I don't suppose there's a simple way to periodically
"audit" index integrity?
> Wasn't really related to this bug. More of a general observation that it
> frequently is a bit verbose...
>
No argument there. I think it does have a --terse flag, but we find the
default verbose output useful occasionally.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Stark | 2014-05-30 00:23:44 | Re: BUG #10432: failed to re-find parent key in index |
| Previous Message | Andres Freund | 2014-05-29 17:19:34 | Re: BUG #10432: failed to re-find parent key in index |