Re: pg_dump error... Follow up

On 8/9/05 3:46 pm, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> Adam Witney <awitney(at)sgul(dot)ac(dot)uk> writes:
>> Here you go....
>
>> pg_filedump-3.0/pg_filedump -i -f -R 34318 34320 134401986.1
>
> Thanks. What it looks like to me is that block 34320 (really 165392)
> is data from some other file altogether. It's evidently still Postgres
> heap data, but instead of having 3 non-null columns as any toast row
> ought to have, these rows have 77 columns many of which are nulls.
> They've got OIDs, too. Possibly you can work out which table these
> rows really belong to. It looks like this ought to be block 415664
> of whatever table it belongs to (which would make it block 22448 of
> the xxx.3 file of that table, if I did the math right).

I only have one file with a .3 in that database... Or could it be from a
different database altogether? (although none of the others get much updates
at all)

Thanks again

adam

--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.