Received: from sss.pgh.pa.us (sss.pgh.pa.us [209.114.132.154]) by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id f0G1bG027022 for ; Mon, 15 Jan 2001 20:37:16 -0500 (EST) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.1/8.11.1) with ESMTP id f0G1akJ29549; Mon, 15 Jan 2001 20:36:46 -0500 (EST) To: Tatsuo Ishii cc: pjw@rhyme.com.au, jhspies@adept.co.za, pgsql-sql@postgresql.org Subject: Re: pg_dump error In-reply-to: <20010116101929G.t-ishii@sra.co.jp> References: <20010115221325.A18814@adept.co.za> <3.0.5.32.20010116120349.02e707d0@mail.rhyme.com.au> <20010116101929G.t-ishii@sra.co.jp> Comments: In-reply-to Tatsuo Ishii message dated "Tue, 16 Jan 2001 10:19:29 +0900" Date: Mon, 15 Jan 2001 20:36:46 -0500 Message-ID: <29546.979609006@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200101/155 X-Sequence-Number: 816 Tatsuo Ishii 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