ERROR: nodeRead: did not find '}' [x2]

Hello,
it seems my postgresql data has somehow become corrupted (by a forced
shutdown I think):

psql template1 -U shadow
Password:
ERROR: nodeRead: did not find '}' at end of plan node
Welcome to psql 7.3.4, the PostgreSQL interactive terminal.

Type: \copyright for distribution terms
\h for help with SQL commands
\? for help on internal slash commands
\g or terminate with semicolon to execute query
\q to quit

template1=> \d
ERROR: current transaction is aborted, queries ignored until end of
transaction block
template1=> abort;
ROLLBACK
template1=> \d
ERROR: nodeRead: did not find '}' at end of plan node

Every command that tries to access a table gives this error...


pg_dumpall says:

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 = 'cinema'
pg_dumpall: pg_dump failed on cinema, exiting


What can I do ?

(postgresql 7.3.4 on a gentoo linux box, with psql from the same package)

---------------------------(end of broadcast)---------------------------
TIP 8: explain analyze is your friend

re: ERROR: nodeRead: did not find '}' [x2]

Andrei Ivanov <andrei.ivanov@ines.ro> writes:[color=blue]
> it seems my postgresql data has somehow become corrupted (by a forced
> shutdown I think):[/color]
[color=blue]
> psql template1 -U shadow
> Password:
> ERROR: nodeRead: did not find '}' at end of plan node[/color]

and
[color=blue]
> 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 = 'cinema'
> pg_dumpall: pg_dump failed on cinema, exiting[/color]

These both look like the pg_user view is corrupted.

It seems hard to believe that identical corruption could have affected
two databases at once. Do you see this same problem with all your
databases (if you have any more than template1 and cinema)? If so,
I wonder whether the postgres executable got corrupted --- it'd not be
very common for a system failure to corrupt files that aren't being
modified, but perhaps it could happen. If it is that, you could fix it
with a quick reinstall of the RPM.

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 7: don't forget to increase your free space map settings