From: | "hubert depesz lubaczewski" <depesz(at)gmail(dot)com> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "Richard Huxton" <dev(at)archonet(dot)com>, "PostgreSQL General" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: corrupted item pointer:??? |
Date: | 2006-04-13 17:30:48 |
Message-ID: | 9e4684ce0604131030p66332b78w32a7d5c3f2c8620c@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 4/13/06, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> "hubert depesz lubaczewski" <depesz(at)gmail(dot)com> writes:
> > On 4/13/06, Richard Huxton <dev(at)archonet(dot)com> wrote:
> >> Hmm - I believe that means a data/index block was corrupted.
> > indices were recreated (reindex table), so i think this is data related
> > problem.
> AFAICS, the only non-index-related occurrence of that error message
> is in PageRepairFragmentation, which is invoked by VACUUM. I'd say
> it indicates a real problem and you shouldn't ignore it. You might
> try using pg_filedump or some such to examine the table and see if
> there's anything obvious about what happened to the corrupted page.
>
i'm not familiar with this utility.
i can of course find it using google, but how do i check what is wrong?
i am even willing to upload the dump file, but with 4 milion records in
table, it is going to be rather large...
pg_relation_size says that the table is about 3g i size
depesz
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2006-04-13 18:10:55 | Re: corrupted item pointer:??? |
Previous Message | hubert depesz lubaczewski | 2006-04-13 17:28:21 | Re: corrupted item pointer:??? |