Return-Path: owner-postman Received: from localhost.Berkeley.EDU (localhost.Berkeley.EDU [127.0.0.1]) by nobozo.CS.Berkeley.EDU (8.6.9/8.6.3) with SMTP id AAA03385 for postgres-redist; Tue, 25 Oct 1994 00:46:15 -0700 Resent-From: POSTGRES mailing list Resent-Message-Id: <199410250746.AAA03385@nobozo.CS.Berkeley.EDU> Sender: owner-postman@postgres.Berkeley.EDU X-Return-Path: owner-postman Received: from faerie.CS.Berkeley.EDU (faerie.CS.Berkeley.EDU [128.32.37.53]) by nobozo.CS.Berkeley.EDU (8.6.9/8.6.3) with ESMTP id AAA03375 for ; Tue, 25 Oct 1994 00:46:14 -0700 Received: from localhost.Berkeley.EDU (localhost.Berkeley.EDU [127.0.0.1]) by faerie.CS.Berkeley.EDU (8.6.9/8.1B) with SMTP id AAA08087; Tue, 25 Oct 1994 00:46:11 -0700 Message-Id: <199410250746.AAA08087@faerie.CS.Berkeley.EDU> X-Authentication-Warning: faerie.CS.Berkeley.EDU: Host localhost.Berkeley.EDU didn't use HELO protocol From: aoki@cs.berkeley.edu (Paul M. Aoki) To: Robert.Patrick@cs.cmu.edu Cc: postgres@postgres.Berkeley.EDU Subject: Re: Postgres Gets Confused! Reply-To: aoki@cs.berkeley.edu (Paul M. Aoki) In-reply-to: Your message of Tue, 25 Oct 1994 02:27:22 -0400 (EDT) Date: Tue, 25 Oct 94 00:46:05 -0700 X-Sender: aoki@postgres.Berkeley.EDU Resent-To: postgres-redist@postgres.Berkeley.EDU X-Mts: smtp Resent-Date: Tue, 25 Oct 94 00:46:15 -0700 Resent-XMts: smtp 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. ==============================================================================