Received: from localhost (maia-2.hub.org [200.46.204.187]) by postgresql.org (Postfix) with ESMTP id 556149FB85B for ; Fri, 9 Mar 2007 13:01:14 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.187]) (amavisd-new, port 10024) with ESMTP id 75191-03-4 for ; Fri, 9 Mar 2007 13:01:09 -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 CE0249FBB3C for ; Fri, 9 Mar 2007 13:01:09 -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 l29H18oi000606; Fri, 9 Mar 2007 11:01:08 -0600 (CST) Date: Fri, 9 Mar 2007 11:01:08 -0600 From: "Glen W. Mabey" To: Tom Lane Cc: PostgreSQL Admin Mailing List Subject: Re: problem upgrading from 8.1.6 to 8.1.8 --- relation does not exist Message-ID: <20070309165925.GE1790@bams.ccf.swri.edu> References: <20070309154013.GA1790@bams.ccf.swri.edu> <502.1173458483@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <502.1173458483@sss.pgh.pa.us> User-Agent: Mutt/1.5.13 (2006-08-11) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.001 tagged_above=0 required=5 tests=BAYES_50 X-Spam-Level: X-Archive-Number: 200703/45 X-Sequence-Number: 24869 On Fri, Mar 09, 2007 at 11:41:23AM -0500, Tom Lane wrote: > "Glen W. Mabey" writes: > > When I SELECT any records from a certain table ("Acquisitions"), I get: > > > acqlibdb=> select * from "Acquisitions"; > > ERROR: relation "Acquisitions" does not exist > > acqlibdb=> select * from public."Acquisitions"; > > ERROR: relation "public.Acquisitions" does not exist > > Maybe it's not in the public schema but some other one (implying you > forgot about a nondefault search_path setting). 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. Is there some way to force an integrity check of the entire database? Thank you for your reply. Glen