Re: problem upgrading from 8.1.6 to 8.1.8 --- relation does not exist - Mailing list pgsql-admin

From Glen W. Mabey
Subject Re: problem upgrading from 8.1.6 to 8.1.8 --- relation does not exist
Date
Msg-id 20070309165925.GE1790@bams.ccf.swri.edu
Whole thread Raw
In response to Re: problem upgrading from 8.1.6 to 8.1.8 --- relation does not exist  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: problem upgrading from 8.1.6 to 8.1.8 --- relation does not exist  ("Glen W. Mabey" <Glen.Mabey@swri.org>)
Re: problem upgrading from 8.1.6 to 8.1.8 --- relation does not exist  ("Igor Neyman" <ineyman@perceptron.com>)
List pgsql-admin
On Fri, Mar 09, 2007 at 11:41:23AM -0500, Tom Lane wrote:
> "Glen W. Mabey" <Glen.Mabey@swri.org> 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

pgsql-admin by date:

Previous
From: "Milen A. Radev"
Date:
Subject: Re: Pg_dump and bytaA
Next
From: "Karthikeyan Sundaram"
Date:
Subject: Running in single instance mode