Обсуждение: pg_dump error
Version 6.5.3 on Debian Potato My daily cron job reported : Can not create pgdump_oid table. Explanation from backend: 'ERROR: cannot create pgdump_oid Is there a way to repair this? Johann -- J.H. Spies - Tel. 082 782 0336 "For I know that my redeemer liveth, and that he shall stand at the latter day uponthe earth" Job 19:25
At 22:13 15/01/01 +0200, Johann Spies wrote: > >Can not create pgdump_oid table. Explanation from backend: 'ERROR: >cannot create pgdump_oid > >Is there a way to repair this? > If there was an earlier crash while running pg_dump, the table may already exist. If so, try deleting it. Also, can you confirm that the username under which you run pg_dump has the rights to create tables? ---------------------------------------------------------------- Philip Warner | __---_____ Albatross Consulting Pty. Ltd. |----/ - \ (A.B.N. 75 008 659 498) | /(@) ______---_ Tel: (+61) 0500 83 82 81 | _________ \ Fax: (+61) 0500 83 82 82 | ___________ | Http://www.rhyme.com.au | / \| | --________-- PGP key available upon request, | / and from pgp5.ai.mit.edu:11371 |/
> >Can not create pgdump_oid table. Explanation from backend: 'ERROR: > >cannot create pgdump_oid > > > >Is there a way to repair this? > > > > If there was an earlier crash while running pg_dump, the table may already > exist. If so, try deleting it. Also, can you confirm that the username > under which you run pg_dump has the rights to create tables? I have observed it several times on 7.0.x while using pg_dumpall. Since pg_dumpall would create pgdump_oid as many times as the number of databases, I suspect there might be an internal cache problem in the backend. However this problem was hard to reproduce, I have not tackled it yet. If someone has a reproducible data, please let us know... -- Tatsuo Ishii
Tatsuo Ishii <t-ishii@sra.co.jp> writes:
>>>> Can not create pgdump_oid table. Explanation from backend: 'ERROR:
>>>> cannot create pgdump_oid
>>>>
>>>> Is there a way to repair this?
I would guess that this means there is a file named "pgdump_oid" hanging
around in the database directory, no doubt leftover from some previous
pg_dump cycle. Manually removing the file should get you up and running
again. However, that just begs the question of why the file is there...
regards, tom lane
On Mon, Jan 15, 2001 at 08:36:46PM -0500, Tom Lane wrote: > Tatsuo Ishii <t-ishii@sra.co.jp> writes: > >>>> Can not create pgdump_oid table. Explanation from backend: 'ERROR: > >>>> cannot create pgdump_oid > >>>> > >>>> Is there a way to repair this? > > I would guess that this means there is a file named "pgdump_oid" hanging > around in the database directory, no doubt leftover from some previous > pg_dump cycle. Manually removing the file should get you up and running > again. However, that just begs the question of why the file is there... > I found the file "pgdump_oid" and removed it. Running the dump script after that resulted in: ------------------------ "$Can not drop pgdump_oid table. Explanation from backend: 'pqReadData() -- backend closed the channel unexpectedly. This probably means the backend terminated abnormally before or while processing the request. '." ------------------------ Running the same script (pg_dump js -o -c -f /home/js/psql/jhspiesdb.out) a second time: ------------------------- 'Can not create pgdump_oid table. Explanation from backend: 'ERROR: cannot create pgdump_oid '. ---------------------------------- Trying after that to "drop table pgdump_oid" resulted in: ------------------------ js=> drop table pgdump_oid; QUERY: drop table pgdump_oid; ERROR: Relation 'pgdump_oid' does not exist ERROR: Relation 'pgdump_oid' does not exist ------------------------ Also doing \dt in psql resulted in an seemingly endless loop with no output produced. I had to kill psql. However, my other applications using postgresql is still working. I also tried reinstalling postgresql. The process also resulted in errors (one was a message about not being able to find a file with the name "can_i_run") and when the installation script (Debian) tried to dump the data it also failed. In the end I had postgresql running again but the same pg_dump problem remains. Regards. Johann -- J.H. Spies - Tel. 082 782 0336 "Jesus said unto her, I am the resurrection, and the life; he that believeth in me,though he were dead, yet shall he live" John 11:25
On Mon, Jan 15, 2001 at 08:36:46PM -0500, Tom Lane wrote: > I would guess that this means there is a file named "pgdump_oid" hanging > around in the database directory, no doubt leftover from some previous > pg_dump cycle. Manually removing the file should get you up and running > again. However, that just begs the question of why the file is there... I found that I could dump another database, but not the one with my data. So there is a problem in my database. Johann -- J.H. Spies - Tel. 082 782 0336 "Jesus said unto her, I am the resurrection, and the life; he that believeth in me,though he were dead, yet shall he live" John 11:25