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 20070309191112.GB2153@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  ("Glen W. Mabey" <Glen.Mabey@swri.org>)
Responses Re: problem upgrading from 8.1.6 to 8.1.8 --- relation does not exist  ("Greg Sabino Mullane" <greg@turnstep.com>)
List pgsql-admin
On Fri, Mar 09, 2007 at 11:01:08AM -0600, Glen W. Mabey wrote:
> 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 a more appropriate list to submit this question to?

Is it possible that this is a bug?

How could I determine whether it is?

Thanks,
Glen

pgsql-admin by date:

Previous
From: Brad Nicholson
Date:
Subject: Re: Running in single instance mode
Next
From: "Igor Neyman"
Date:
Subject: Re: problem upgrading from 8.1.6 to 8.1.8 --- relation does not exist