| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Steve Wampler <swampler(at)noao(dot)edu> |
| Cc: | postgres-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: pg_dump dying (and VACUUM ANALYZE woes)... |
| Date: | 2001-04-13 17:03:04 |
| Message-ID: | 4715.987181384@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Steve Wampler <swampler(at)noao(dot)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 from the 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Steve Wolfe | 2001-04-13 17:12:42 | Re: Shared memory failure? |
| Previous Message | Tom Lane | 2001-04-13 16:50:12 | Re: Using pl/pgsql or sql for in/out functions for types |