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

Поиск
Список
Период
Сортировка
Искать
От
Andrei Ivanov
Тема
Re: ERROR: nodeRead: did not find '}' [x2]
Дата
Msg-id
Pine.LNX.4.58L0.0311202226000.29930@webdev.ines.ro
Ответ на
Список
Дерево обсуждения
ERROR: nodeRead: did not find '}' [x2] Andrei Ivanov <andrei.ivanov@ines.ro>
Re: ERROR: nodeRead: did not find '}' [x2] Tom Lane <tgl@sss.pgh.pa.us>
Re: ERROR: nodeRead: did not find '}' [x2] Andrei Ivanov <andrei.ivanov@ines.ro>
Re: ERROR: nodeRead: did not find '}' [x2] Tom Lane <tgl@sss.pgh.pa.us>
Re: ERROR: nodeRead: did not find '}' [x2] Andrei Ivanov <andrei.ivanov@ines.ro>
Re: ERROR: nodeRead: did not find '}' [x2] Tom Lane <tgl@sss.pgh.pa.us>
Re: ERROR: nodeRead: did not find '}' [x2] Andrei Ivanov <andrei.ivanov@ines.ro>
Re: ERROR: nodeRead: did not find '}' [x2] Tom Lane <tgl@sss.pgh.pa.us>
Re: ERROR: nodeRead: did not find '}' [x2] Andrei Ivanov <andrei.ivanov@ines.ro>
Re: ERROR: nodeRead: did not find '}' [x2] Tom Lane <tgl@sss.pgh.pa.us>
Re: ERROR: nodeRead: did not find '}' [x2] Andrei Ivanov <andrei.ivanov@ines.ro>

I've reinstalled postgres, but the same errors happen. 
I've tried connection to more databases, but the error show everytime.

psql -U shadow dc
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

dc=> \dt
ERROR:  current transaction is aborted, queries ignored until end of 
transaction block
dc=> 

???

This is the log from when the forced system shutdown happened:

LOG:  pq_recvbuf: unexpected EOF on client connection
LOG:  pq_recvbuf: unexpected EOF on client connection
LOG:  pq_recvbuf: unexpected EOF on client connection
LOG:  fast shutdown request
LOG:  shutting down
LOG:  database system is shut down
LOG:  database system was shut down at 2003-11-06 23:21:03 EET
LOG:  checkpoint record is at 0/7CDAC94
LOG:  redo record is at 0/7CDAC94; undo record is at 0/0; shutdown TRUE
LOG:  next transaction id: 115743; next oid: 205535
LOG:  database system is ready
LOG:  database system was interrupted at 2003-11-06 23:21:05 EET
LOG:  checkpoint record is at 0/7CDAC94
LOG:  redo record is at 0/7CDAC94; undo record is at 0/0; shutdown TRUE
LOG:  next transaction id: 115743; next oid: 205535
LOG:  database system was not properly shut down; automatic recovery in 
progress
LOG:  ReadRecord: record with zero length at 0/7CDACD4
LOG:  redo is not required
LOG:  database system is ready


On Thu, 20 Nov 2003, Tom Lane wrote:

> Andrei Ivanov  writes:
> > 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
> 
> and
> 
> > 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
> 
> 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
> 
В списке pgsql-general по дате отправления
От: Andrew Sullivan
Дата:
От: Rick Gigger
Дата:
Сообщение: Re: performance problem
FAQ