From: Johann Spies <jhspies@adept.co.za>
To: pgsql-sql@postgresql.org
Subject: Re: pg_dump error - further information
Date: Tue, 16 Jan 2001 10:46:44 +0200
Message-ID: <20010116104644.A1198@adept.co.za> (raw)
In-Reply-To: <29546.979609006@sss.pgh.pa.us>
References: <20010115221325.A18814@adept.co.za>
<3.0.5.32.20010116120349.02e707d0@mail.rhyme.com.au>
<20010116101929G.t-ishii@sra.co.jp>
<29546.979609006@sss.pgh.pa.us>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-sql@postgresql.org
Cc: jhspies@adept.co.za
Subject: Re: pg_dump error - further information
In-Reply-To: <20010116104644.A1198@adept.co.za>
References: <20010115221325.A18814@adept.co.za> <3.0.5.32.20010116120349.02e707d0@mail.rhyme.com.au> <20010116101929G.t-ishii@sra.co.jp> <29546.979609006@sss.pgh.pa.us> <20010116104644.A1198@adept.co.za>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox