Re: problem upgrading from 8.1.6 to 8.1.8 --- relation <tablename> does not exist

From: "Glen W(dot) Mabey" <Glen(dot)Mabey(at)swri(dot)org>
To: PostgreSQL Admin Mailing List <pgsql-admin(at)postgresql(dot)org>
Subject: Re: problem upgrading from 8.1.6 to 8.1.8 --- relation <tablename> does not exist
Date: 2007-03-09 19:11:12
Message-ID: 20070309191112.GB2153@bams.ccf.swri.edu
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(dot)Mabey(at)swri(dot)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

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Scott Marlowe 2007-03-09 19:58:31 Re: index not being used. Why?
Previous Message Brad Nicholson 2007-03-09 19:01:11 Re: Running in single instance mode