Re: Incomplete pg_dump operation

xyz is the largest table in the database, and the one identified in prior error messages.

After su'ing to pgsql, I executed a:

pg_dump -t xyz database_name > /usr/local/pgsql/db_backups/database_name-Manual-Xyz-Table-Dump

command, and this message was returned:

pg_dump: ERROR: could not open relation with OID 2196359751
pg_dump: SQL command to dump the contents of table "xyz" failed: PQendcopy() failed.
pg_dump: Error message from server: ERROR: could not open relation with OID 2196359751
pg_dump: The command was: COPY public.xyz ({various field names}) TO stdout;

That's the same OID other error messages have complained about.

About 1/3 of the database was dumped to the destination file before this error message was displayed.

-------

At 10:37 AM 2/8/2010, Tom Lane wrote:
>peter(at)vfemail(dot)net writes:
>> The first execution of the:
>
>> select * from pg_index where indexrelid = 2196359751;
>
>> command returned this message:
>
>> WARNING: terminating connection because of crash of another server process
>
>It seems you have much worse problems than this one table. I think you
>need to plan on re-initdb'ing and re-loading. If you can't get pg_dump
>to produce a whole dump, does it work to dump one table at a time with
>the -t switch?
>
> regards, tom lane