Received: from localhost (unknown [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id 0E95A2E46F5 for ; Wed, 23 Jan 2008 17:07:37 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.182]) (amavisd-maia, port 10024) with ESMTP id 70921-01-2 for ; Wed, 23 Jan 2008 17:07:29 -0400 (AST) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id D929B2E2D8D for ; Wed, 23 Jan 2008 16:57:03 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.2/8.14.2) with ESMTP id m0NKuwr5025325; Wed, 23 Jan 2008 15:56:58 -0500 (EST) To: "Mark Steben" cc: pgsql-admin@postgresql.org Subject: Re: no entry on pg_database for a live database In-reply-to: <003801c85e00$89934480$14010a0a@dei26g028575> References: <003801c85e00$89934480$14010a0a@dei26g028575> Comments: In-reply-to "Mark Steben" message dated "Wed, 23 Jan 2008 15:42:58 -0500" Date: Wed, 23 Jan 2008 15:56:58 -0500 Message-ID: <25324.1201121818@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200801/230 X-Sequence-Number: 28004 "Mark Steben" 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