Skip site navigation (1) Skip section navigation (2)

Re: Bug #698: Error haciendo Backup con pg_dump!!

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: christiangda(at)cantv(dot)net, pgsql-bugs(at)postgresql(dot)org
Subject: Re: Bug #698: Error haciendo Backup con pg_dump!!
Date: 2002-06-25 22:28:46
Message-ID: 11374.1025044126@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-bugspgsql-odbc
pgsql-bugs(at)postgresql(dot)org writes:
> [avl(at)bdserver avl]$  nohup pg_dump -R -O leemail2 | gzip -c > /tmp/resp.leemail2_25_6_2002_1_00_pm.sql.gz &
> [avl(at)bdserver avl]$ jobs
> [1]+  Running                 nohup pg_dump -R -O leemail2 | gzip -c >/tmp/resp.leemail2_25_6_2002_1_00_pm.sql.gz &
> [avl(at)bdserver avl]$ ERROR:  MemoryContextAlloc: invalid request size 4294967293
> PQendcopy: resetting connection
> SQL query to dump the contents of Table 'datamailentrada_historico' did not execute correctly.  After we read all the table contents from the backend, PQendcopy() failed.  Explanation from backend: ''.
> The query was: 'COPY "datamailentrada_historico" TO stdout;

This looks like you have some corrupted data in
datamailentrada_historico :-(.

There is not much you can do about this except try to identify and
remove the damaged row(s).  You can look in the mailing list archives
for previous discussions about systematic ways to identify the location
of the damage, but basically you want to home in on which row(s) can't
be selected without provoking the error.

Once you've removed the damaged rows, you may be fortunate enough to be
able to restore them from a recent backup.  Good luck!

			regards, tom lane



In response to

pgsql-odbc by date

Next:From: Webb SpragueDate: 2002-06-25 23:50:38
Subject: "Field is too small"
Previous:From: pgsql-bugsDate: 2002-06-25 18:42:01
Subject: Bug #698: Error haciendo Backup con pg_dump!!

pgsql-bugs by date

Next:From: Webb SpragueDate: 2002-06-25 23:50:38
Subject: "Field is too small"
Previous:From: David M. KaplanDate: 2002-06-25 22:14:18
Subject: view OIDs

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group