agora inbox for postgres@postgres.berkeley.edu  

help / color / mirror / Atom feed

From: Paul M. Aoki <aoki@cs.berkeley.edu>
To: Robert.Patrick@cs.cmu.edu
Cc: postgres@postgres.Berkeley.EDU
Subject: Re: Postgres Gets Confused!
Date: Tue, 25 Oct 94 00:46:05 -0700
Message-ID: <199410250746.AAA08087@faerie.CS.Berkeley.EDU> (raw)
In-Reply-To: <Eif_J_i00hMd8ZKG5w@cs.cmu.edu>

Robert.Patrick@cs.cmu.edu writes:
> 1.) Claims the user is not a valid user even though they have been using
> the system not 5 minutes before. 
> 2.) Claims the database does not exist even though they had been using
> it not 5 minutes earlier and it is still listed under the base
> subdirectory. 
> Most of the time, I can cure this problem by logging in removing the
> user and re-adding them.

most of the time when i used to see this it was the funny PGUSER
environment variable corruption thing.  if you already patched around
that one then i'm not sure what it is.  try killing the postmaster and
restarting it (without blowing away the old database) and see if that
clears up the problem temporarily.  (there was a problem with the fact
that when you destroydb then createdb you sometimes leave the shared
memory buffer pool in a funny state.  i don't think this was ever
resolved.)

> Also, there seems to be a bug in the parser/planner.  First, it tells me
> that I must use an explicit cast (see below), which makes perfect sense.
>  Then, I use an explicit cast and it tells me that I cannot do cast this
> expression (huh?).
> * retrieve (pg_operator.oprname) where pg_operator.oprleft = 16::oid\g 

shameful to say,
   retrieve (pg_operator.oprname) where pg_operator.oprleft = "16"::oid\g
works..
--
  Paul M. Aoki          |  University of California at Berkeley
  aoki@CS.Berkeley.EDU  |  Dept. of EECS, Computer Science Division (#1776) 
                        |  Berkeley, CA 94720-1776

==============================================================================
   To add/remove yourself to/from the POSTGRES mailing list: send mail with 
   the subject line ADD or DEL to "postgres-request@postgres.Berkeley.EDU"

   If this fails, send mail to "post_questions@postgres.Berkeley.EDU" and
   a human will deal with it.  DO NOT post to the "postgres" mailing list.
==============================================================================

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: postgres@postgres.berkeley.edu
  Cc: aoki@cs.berkeley.edu, Robert.Patrick@cs.cmu.edu
  Subject: Re: Postgres Gets Confused!
  In-Reply-To: <199410250746.AAA08087@faerie.CS.Berkeley.EDU>

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

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