pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Martin Sarsale <lists@runa.sytes.net>
Cc: pgsql-admin@postgresql.org
Subject: Re: nodeRead: did not find '}' at end of plan node
Date: Mon, 15 Mar 2004 17:07:09 -0500
Message-ID: <8062.1079388429@sss.pgh.pa.us> (raw)
In-Reply-To: <20040315180703.5e27de95.lists@runa.sytes.net>
References: <20040315180703.5e27de95.lists@runa.sytes.net>

Martin Sarsale <lists@runa.sytes.net> 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



view thread (4+ messages)  latest in thread

Message-ID: <8062.1079388429@sss.pgh.pa.us>
Permalink:  ../8062.1079388429@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/8062.1079388429@sss.pgh.pa.us

 · 

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: tgl@sss.pgh.pa.us, lists@runa.sytes.net
  Subject: Re: nodeRead: did not find '}' at end of plan node
  In-Reply-To: <8062.1079388429@sss.pgh.pa.us>
  References: <20040315180703.5e27de95.lists@runa.sytes.net> <8062.1079388429@sss.pgh.pa.us>

* 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