From: Tom Lane <tgl@sss.pgh.pa.us>
To: frant101@googlemail.com
Cc: pgsql-admin@postgresql.org
Subject: Re: pg_dumpall error
Date: Tue, 13 Nov 2007 11:54:50 -0500
Message-ID: <17882.1194972890@sss.pgh.pa.us> (raw)
In-Reply-To: <1194950275.303346.276410@v3g2000hsg.googlegroups.com>
References: <1194950275.303346.276410@v3g2000hsg.googlegroups.com>
frant101@googlemail.com writes:
> pg_dump: SQL command failed
> pg_dump: Error message from server: ERROR: relation
> "esales.invoiceline" does not exist
> pg_dump: The command was: LOCK TABLE esales.invoiceline IN ACCESS
> SHARE MODE
> pg_dumpall: pg_dump failed on database "hermes", exiting
> The esales.invoiceline table is there are can be accessed.
You mean that if you issue the same command by hand, it works? That
would be bizarre.
> We are running PostgreSQL 8.1.3 and the pg_dumpall command is
Update to something current (preferably 8.1.10). Then try REINDEXing
pg_class.
regards, tom lane
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 using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, frant101@googlemail.com
Subject: Re: pg_dumpall error
In-Reply-To: <17882.1194972890@sss.pgh.pa.us>
* 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