Re: pg_dump dying (and VACUUM ANALYZE woes)... - Mailing list pgsql-general

From Tom Lane
Subject Re: pg_dump dying (and VACUUM ANALYZE woes)...
Date
Msg-id 4715.987181384@sss.pgh.pa.us
Whole thread Raw
In response to pg_dump dying (and VACUUM ANALYZE woes)...  (Steve Wampler <swampler@noao.edu>)
List pgsql-general
Steve Wampler <swampler@noao.edu> writes:
> I'm getting the following error from pg_dump when trying to
> dump a particular database:
> ==============================================================
> -> pg_dump logdb >logdb.dump
> pqWait() -- connection not open
> PQendcopy: resetting connection
> SQL query to dump the contents of Table 'messages' did not execute correctly.  After we read all the table contents
fromthe backend, PQendcopy() failed.  Explanation from backend: 'The Data Base System is starting up 
> '.
> The query was: 'COPY "messages" TO stdout;
> '.
> ==============================================================
> About 25MB has been dumped when this error occurs.  (There's 15GB
> free on the disk partition.)

Looks like you've got corrupted data in that table (clobbered length
word in some variable-length field, most likely).

            regards, tom lane

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: Deadlock detected
Next
From: Tom Lane
Date:
Subject: Re: Using pl/pgsql or sql for in/out functions for types