Received: from localhost (maia-3.hub.org [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id 388E29FB423 for ; Mon, 12 Mar 2007 12:03:49 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-new, port 10024) with ESMTP id 49529-02 for ; Mon, 12 Mar 2007 12:03:43 -0300 (ADT) 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 633AE9FB2C0 for ; Mon, 12 Mar 2007 12:03:44 -0300 (ADT) Received: from gwmdc1293linux (localhost [127.0.0.1]) by virus89-out.ccf.swri.edu (8.13.1/8.13.1) with ESMTP id l2CF3bAp013266; Mon, 12 Mar 2007 10:03:38 -0500 (CDT) Date: Mon, 12 Mar 2007 10:03:37 -0500 From: "Glen W. Mabey" To: Tom Lane Cc: Greg Sabino Mullane , pgsql-admin@postgresql.org Subject: Re: problem upgrading from 8.1.6 to 8.1.8 --- relation does not exist Message-ID: <20070312150337.GA32491@bams.ccf.swri.edu> References: <20070309191112.GB2153@bams.ccf.swri.edu> <5140152e00e28ac90209884943d60d3d@biglumber.com> <20070309205603.GF2153@bams.ccf.swri.edu> <4499.1173482961@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4499.1173482961@sss.pgh.pa.us> User-Agent: Mutt/1.5.13 (2006-08-11) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200703/66 X-Sequence-Number: 24890 On Fri, Mar 09, 2007 at 06:29:21PM -0500, Tom Lane wrote: > "Glen W. Mabey" writes: > > 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. > > I wonder whether "reindex index pg_class_relname_nsp_index" would make > this go away. Great -- that did it. However, after I executed that command, SELECT FROM "Acquisitions" LIMIT 1; still indicated that "Acquisitions" did not exist. But then a pg_dump command succeeded, and afterwared, SELECT FROM "Acquisitions" LIMIT 1; did also succeed. Thank you very much for your help. Is this a bug that should be reported? And, what does "reindex index pg_class_relname_nsp_index" do, anyway? Also, there is another user who has posted to this list describing what I first saw when encountering this problem: trouble running pg_dump. Thanks, Glen