Re: pg_dump fails - Mailing list pgsql-general

From Tom Lane
Subject Re: pg_dump fails
Date
Msg-id 26163.1113860765@sss.pgh.pa.us
Whole thread Raw
In response to pg_dump fails  (Lorenzo Thurman <lorenzo@thethurmans.com>)
Responses Re: pg_dump fails  (Lorenzo Thurman <lorenzo@thethurmans.com>)
List pgsql-general
Lorenzo Thurman <lorenzo@thethurmans.com> writes:
> pg_dump: Error message from server: ERROR:  did not find '}' at end of
> input node
> pg_dump: The command was: SELECT (SELECT usename FROM pg_user WHERE
> usesysid = datdba) as dba, pg_encoding_to_char(encoding) as encoding,
> datpath FROM pg_database WHERE datname = 'printstats'

This suggests that there's something wrong with the pg_user view ---
specifically, that the stored view rule isn't in the format that the
backend expects.

I don't recall ever having seen that error in the field, only in
development builds that someone had been sloppy about fully rebuilding
after a CVS update (so that the code inside the server wasn't fully
self-consistent).  Where did you get your postgres executable from,
exactly?

Also, does "select * from pg_user" provoke the same error in every
database of your installation, or only this one?  If the latter,
it could be a data-corruption kind of problem.

            regards, tom lane

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: Plpgsql function with unknown number of args
Next
From: Bruce Momjian
Date:
Subject: Re: PostgreSQL Database cluster with multiple different locale