| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pg_filedump strangeness |
| Date: | 2010-04-06 22:33:59 |
| Message-ID: | 20100406223359.GG3491@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane wrote:
> Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> > I'm chasing an apparent index corruption problem, and I came across
> > something I can't quite explain in pg_filedump. Say I dump a non-leaf
> > btree index page:
>
> I think this is actually OK. Remember that in a non-rightmost page,
> item 1 is the high key not a data entry.
Oh, BTW, this is not what's corrupted about this index -- I just had
trouble following what pg_filedump was reporting. The corruption is
more subtle: vacuum cannot find the parent page when trying to mark a
page for deletion.
--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2010-04-06 22:48:52 | Re: Win32 timezone matching |
| Previous Message | Alvaro Herrera | 2010-04-06 22:31:47 | Re: pg_filedump strangeness |