X-Original-To: pgsql-general-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 28D06535D8 for ; Sun, 10 Apr 2005 17:28:07 +0100 (BST) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 85547-03 for ; Sun, 10 Apr 2005 16:27:57 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id 3DD6F533E9 for ; Sun, 10 Apr 2005 17:27:56 +0100 (BST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id j3AGRtj5028690; Sun, 10 Apr 2005 12:27:55 -0400 (EDT) To: PFC Cc: pgsql-general@postgresql.org Subject: Re: pg 8.0.1-r3 killls pgadmin3 and phppgadmin In-reply-to: References: <5852.1112819444@sss.pgh.pa.us> Comments: In-reply-to PFC message dated "Sun, 10 Apr 2005 13:52:20 +0200" Date: Sun, 10 Apr 2005 12:27:55 -0400 Message-ID: <28689.1113150475@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.006 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200504/455 X-Sequence-Number: 76368 PFC writes: > I've traced it to the following query to get information about the > database : > SELECT pdb.datname AS datname, pu.usename AS datowner, > pg_encoding_to_char(encoding) AS datencoding, > (SELECT description FROM pg_description pd WHERE pdb.oid=pd.objoid) AS > datcomment, > (SELECT spcname FROM pg_catalog.pg_tablespace pt WHERE > pt.oid=pdb.dattablespace) AS tablespace > FROM pg_database pdb, pg_user pu > WHERE pdb.datdba = pu.usesysid AND NOT pdb.datistemplate > ORDER BY pdb.datname; Works for me. > This query looks right to me and pg 8.0.0 does it fine, while 8.0.1-r3 > says : > Error : Unexpected right parenthesis. Hmm; the only occurrence of that string in the sources is in nodes/read.c, which AFAIK would never be invoked for a query entered straight from the client. What could trigger it would be trying to read a rule that is misformatted for some reason. Maybe you have a damaged pg_user view definition --- does "select * from pg_user" fail the same way? regards, tom lane