"Joe Shevland" <shevlandj@kpi.com.au> writes:
> Semi-topical I hope ;)
Completely irrelevant to JDBC as far as I can see. I've redirected to
pghackers.
> NOTICE: Rel pg_attribute: TID 1/115: OID IS INVALID. TUPGONE 1.
> ...
> NOTICE: Rel pg_attribute: TID 1/6087: OID IS INVALID. TUPGONE 1.
> NOTICE: Rel pg_attribute: TID 1/6111: OID IS INVALID. TUPGONE 1.
> NOTICE: Rel pg_attribute: TID 1/6112: OID IS INVALID. TUPGONE 1.
> NOTICE: Rel pg_attribute: TID 1/6136: OID IS INVALID. TUPGONE 1.
> NOTICE: Rel pg_attribute: TID 1/6137: OID IS INVALID. TUPGONE 1.
> pqReadData() -- backend closed the channel unexpectedly.
> This probably means the backend terminated abnormally
> before or while processing the request.
Ugh. It looks like something has clobbered your pg_attribute file.
Was this the first sign of trouble? Can you provide an "od -x" dump of
that file? (It'd be $PGDATA/base/DB2OID/1249; you'll need to look in
pg_database to determine the OID of db2.)
regards, tom lane
