X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 2F1D58B9F36 for ; Fri, 4 Feb 2005 17:08:29 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 29933-07 for ; Fri, 4 Feb 2005 17:08:26 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id 8C6738B9EB8 for ; Fri, 4 Feb 2005 17:08:26 +0000 (GMT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id j14H8PKq015307; Fri, 4 Feb 2005 12:08:25 -0500 (EST) To: Gary Jackson Cc: pgsql-admin@postgresql.org Subject: Re: Downlevel database In-reply-to: <27afcdf4f7f6c6de86d93dc87d9bb6ec@umiacs.umd.edu> References: <27afcdf4f7f6c6de86d93dc87d9bb6ec@umiacs.umd.edu> Comments: In-reply-to Gary Jackson message dated "Fri, 04 Feb 2005 11:48:00 -0500" Date: Fri, 04 Feb 2005 12:08:25 -0500 Message-ID: <15306.1107536905@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.006 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200502/36 X-Sequence-Number: 16204 Gary Jackson writes: > We have a problem with a PosgreSQL database where the user cannot get > to their tables any more. I am not the primary administrator of this > host (who is on vacation), nor am I the user of this database. The > /var/log/posgresql file has entries like the following, at the end: > FATAL 1: Database "trees_rock" does not exist in the system catalog. > The current running version of the database is 7.2.2, and I suspect the > database was created and maintained with 7.3.4 (after examining the > bash history file for user postgres). > Would running downlevel software cause this problem? Does this seem > likely or possible? No, no, and no. A 7.2.anything server would flat out refuse to start in a 7.3.* database (because it checks PG_VERSION). You might have been using 7.3 client-side code to talk to the 7.2 server, but that wouldn't cause this sort of failure. A possible quick-and-dirty solution is "VACUUM pg_database" (issued from any of the databases that you can get into). If that doesn't work then you've got serious problems :-( regards, tom lane