pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Glen W. Mabey <Glen.Mabey@swri.org>
To: Igor Neyman <ineyman@perceptron.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: PostgreSQL Admin Mailing List <pgsql-admin@postgresql.org>
Subject: Re: problem upgrading from 8.1.6 to 8.1.8 --- relation <tablename> does not exist
Date: Fri, 9 Mar 2007 14:34:20 -0600
Message-ID: <20070309203420.GD2153@bams.ccf.swri.edu> (raw)
In-Reply-To: <F4C27E77F7A33E4CA98C19A9DC6722A201B8086E@EXCHANGE.corp.perceptron.com>
References: <20070309154013.GA1790@bams.ccf.swri.edu>
	<502.1173458483@sss.pgh.pa.us>
	<20070309165925.GE1790@bams.ccf.swri.edu>
	<F4C27E77F7A33E4CA98C19A9DC6722A201B8086E@EXCHANGE.corp.perceptron.com>


The definition of the View refers to just "Acquisitions".

Glen

On Fri, Mar 09, 2007 at 03:20:51PM -0500, Igor Neyman wrote:
> Why wouldn't you look at the definition of the view which is based on
> this table (and which you claim is still working), and how it references
> basic table?
> M.b. it'll point you to the actual table location.
> 
> Igor 
> 
> -----Original Message-----
> From: pgsql-admin-owner@postgresql.org
> [mailto:pgsql-admin-owner@postgresql.org] On Behalf Of Glen W. Mabey
> Sent: Friday, March 09, 2007 12:01 PM
> To: Tom Lane
> Cc: PostgreSQL Admin Mailing List
> Subject: Re: [ADMIN] problem upgrading from 8.1.6 to 8.1.8 --- relation
> <tablename> does not exist
> 
> 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
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 2: Don't 'kill -9' the postmaster
> 



view thread (10+ messages)  latest in thread

Message-ID: <20070309203420.GD2153@bams.ccf.swri.edu>
Permalink:  ../20070309203420.GD2153@bams.ccf.swri.edu/
Also on:    postgresql.org/message-id/20070309203420.GD2153@bams.ccf.swri.edu

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: Glen.Mabey@swri.org, ineyman@perceptron.com, tgl@sss.pgh.pa.us
  Subject: Re: problem upgrading from 8.1.6 to 8.1.8 --- relation <tablename> does not exist
  In-Reply-To: <20070309203420.GD2153@bams.ccf.swri.edu>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox