Re: no entry on pg_database for a live database

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Mark Steben" <msteben(at)autorevenue(dot)com>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: no entry on pg_database for a live database
Date: 2008-01-23 20:56:58
Message-ID: 25324.1201121818@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

"Mark Steben" <msteben(at)autorevenue(dot)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

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Alexander Vysokovskih 2008-01-23 20:59:02 lost /pg_xlog
Previous Message Mark Steben 2008-01-23 20:42:58 Re: no entry on pg_database for a live database