Error when trying to use pg_dump on 8.3 after minor release update

From: Joshua Berry <yoberi(at)gmail(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Error when trying to use pg_dump on 8.3 after minor release update
Date: 2009-10-23 16:06:10
Message-ID: 5ccd53c10910230906t7f469821se225665252c51e88@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Greetings,

I get the following error when I try to dump a database on a production server:

[jberry(at)dms dms]$ pg_dump -U dms_user -s dms > dms_s.sql
pg_dump: SQL command failed
pg_dump: Error message from server: ERROR:  could not open relation
with OID 27224
pg_dump: The command was: SELECT
pg_catalog.pg_get_viewdef('27289'::pg_catalog.oid) as viewdef

It is a RHEL 5 x86_64 server, running 8.3.7/8

Since the previous backup, we upgraded (via yum) the server from 8.3.7
to 8.3.8 without a restart.

With this error, I'm concerned about stopping and starting postgresql
to see if the error goes away: I don't want us to be left with a dead
database and no backup with the latest data.

So, is this expected behavior when you fail to restart after a minor
version upgrade, or is this a sign of hardware failure and we should
try dumping relations one at a time?

Regards,
-Joshua Berry

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Sam Mason 2009-10-23 16:07:19 Re: Question of using trigger's OLD in EXECUTE
Previous Message Tom Lane 2009-10-23 16:03:52 Re: pg 8.4 (Auto)-vacuumlo