X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 626D9D1E317 for ; Mon, 15 Mar 2004 22:07:11 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 07727-09 for ; Mon, 15 Mar 2004 18:07:11 -0400 (AST) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by svr1.postgresql.org (Postfix) with ESMTP id 91F5ED1E146 for ; Mon, 15 Mar 2004 18:07:08 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.11/8.12.11) with ESMTP id i2FM7A2L008063; Mon, 15 Mar 2004 17:07:10 -0500 (EST) To: Martin Sarsale Cc: pgsql-admin@postgresql.org Subject: Re: nodeRead: did not find '}' at end of plan node In-reply-to: <20040315180703.5e27de95.lists@runa.sytes.net> References: <20040315180703.5e27de95.lists@runa.sytes.net> Comments: In-reply-to Martin Sarsale message dated "Mon, 15 Mar 2004 18:07:03 -0300" Date: Mon, 15 Mar 2004 17:07:09 -0500 Message-ID: <8062.1079388429@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200403/227 X-Sequence-Number: 12796 Martin Sarsale writes: > Im running psql (PostgreSQL) 7.3.2 here and since some weeks Im getting this error when trying to dump all databases (to upgrade to pg 7.4.1) > \connect XXX > pg_dump: SQL command failed > pg_dump: Error message from server: ERROR: nodeRead: did not find '}' at end of plan node > pg_dump: The command was: select (select usename from pg_user where usesysid = datdba) as dba, encoding, datpath from pg_database where datname = 'emepe3' > pg_dumpall: pg_dump failed on emepe3, exiting It would appear that the view rule for the pg_user view is corrupt, or at least not quite the same format that the backend code is expecting. Can you do "select * from pg_user" in any of your databases, or does it fail the same way in all? If it fails in each database then I'd suspect some kind of version mismatch; if not then it's just corrupt in that particular database. We had a similar report last November which seemed to be related to a glibc update --- see the thread starting here: http://archives.postgresql.org/pgsql-general/2003-11/msg01102.php The complainant lost interest after finding a workaround, so we never did get a complete explanation of what happened, but I'm suspicious there was some software incompatibility involved, not data corruption per se. I would like to find out the truth of the matter. If you are interested you could try manually creating an equivalent of pg_user, viz CREATE VIEW my_pg_user AS SELECT usename, usesysid, usecreatedb, usesuper, usecatupd, '********'::text as passwd, valuntil, useconfig FROM pg_shadow; and then see if you can do "select * from my_pg_user", and if so, what is the difference between the pg_rewrite entries for the two views. (See the above-referenced thread for more info.) regards, tom lane