From: Tom Lane <tgl@sss.pgh.pa.us>
To: Mark Steben <msteben@autorevenue.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: no entry on pg_database for a live database
Date: Wed, 23 Jan 2008 15:56:58 -0500
Message-ID: <25324.1201121818@sss.pgh.pa.us> (raw)
In-Reply-To: <003801c85e00$89934480$14010a0a@dei26g028575>
References: <003801c85e00$89934480$14010a0a@dei26g028575>
"Mark Steben" <msteben@autorevenue.com> writes:
> Thanks Tom - that did the trick
In that case, you were missing pg_database and probably other system
catalogs too in your vacuuming.
> We will be upgrading to 8.2 within the next couple weeks.
I'd recommend making sure you have vacuumed all system catalogs before
you try to pg_dump, else some of the catalog entries may be invisible
to pg_dump :-(
FWIW, 8.2 should be proof against this type of problem recurring,
because it takes proactive steps to avoid transaction ID wraparound.
7.4 left that up to the DBA ...
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, msteben@autorevenue.com
Subject: Re: no entry on pg_database for a live database
In-Reply-To: <25324.1201121818@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