Received: from localhost (maia-5.hub.org [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id BA4CD9FB5FA for ; Fri, 9 Mar 2007 16:56:08 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.182]) (amavisd-new, port 10024) with ESMTP id 35015-05 for ; Fri, 9 Mar 2007 16:56:02 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from virus89-out.ccf.swri.edu (virus89-out.ccf.swri.edu [129.162.252.34]) by postgresql.org (Postfix) with ESMTP id EA7BA9FB5E4 for ; Fri, 9 Mar 2007 16:56:04 -0400 (AST) Received: from gwmdc1293linux (localhost [127.0.0.1]) by virus89-out.ccf.swri.edu (8.13.1/8.13.1) with ESMTP id l29Ku3qj013288; Fri, 9 Mar 2007 14:56:03 -0600 (CST) Date: Fri, 9 Mar 2007 14:56:03 -0600 From: "Glen W. Mabey" To: Greg Sabino Mullane Cc: pgsql-admin@postgresql.org Subject: Re: problem upgrading from 8.1.6 to 8.1.8 --- relation does not exist Message-ID: <20070309205603.GF2153@bams.ccf.swri.edu> References: <20070309191112.GB2153@bams.ccf.swri.edu> <5140152e00e28ac90209884943d60d3d@biglumber.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5140152e00e28ac90209884943d60d3d@biglumber.com> User-Agent: Mutt/1.5.13 (2006-08-11) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200703/54 X-Sequence-Number: 24878 On Fri, Mar 09, 2007 at 08:51:44PM +0000, Greg Sabino Mullane wrote: > > Hash: RIPEMD160 > > > > > > When I SELECT any records from a certain table ("Acquisitions"), I get: > > > > > > > acqlibdb=> select * from "Acquisitions"; > > > > ERROR: relation "Acquisitions" does not exist > ..> > > Humm. I don't think so, since I've never altered the search_path > > settings, nor used any schema besides public. And I've been working > > with this database for 8 months now without ever encountering such an > > error. And all of the other tables work just fine. > > See what this gives you: > > SELECT nspname, relname, relkind > FROM pg_class c, pg_namespace n > WHERE c.relnamespace = n.oid > AND lower(relname) ~ 'acqu' > ORDER BY 2,1,3; I have no idea what that does, but here is the output: nspname | relname | relkind ---------+------------------------------+--------- public | Acquisition_pkey | i public | Acquisitions | r public | Acquisitions_id_seq | S public | Acquisitions_location_id_key | i public | ViewAcquisitions | v public | viewacquisitionsnew | v What I see is a bunch of stuff related to the Acquisitions table, including a relation for the primary key, which was created back when the table was named "Acquisition" (not plural), and two different views which draw on Acquisitions, both of which appear to be fully functional. Thanks for you reply -- Glen