Strange error

From: Csaba Nagy <nagy(at)ecircle-ag(dot)com>
To: Postgres general mailing list <pgsql-general(at)postgresql(dot)org>
Subject: Strange error
Date: 2005-10-17 15:21:20
Message-ID: 1129562480.2995.292.camel@coppola.muc.ecircle.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hi all,

I wonder what caused the error we just got on a postgres 8.0.3 data base
(using JDBC to connect, but I guess that's not really relevant for this
error):

[snip stack trace]
Caused by: org.postgresql.util.PSQLException: ERROR: could not access
status of transaction 0
[snip]

Could it be some kind of data corruption?

The data base was created/started up using the hot-standby procedure
described here:
http://www.postgresql.org/docs/8.0/static/backup-online.html
with some custom archive_command/restore_command scripts in place to
keep the standby running and up to date.

This time it was actually the switch back from the original stand-by
functioning now as master after we had to put it in production after the
original master machine stopped responding (which later turned out to be
caused by a too many files opened in the system error).

The machine is still running without restart after finishing recovery. I
wonder if restarting it will solve any reminiscent problems or some more
work is needed ?

TIA,
Csaba.

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Csaba Nagy 2005-10-17 15:26:38 Re: Strange error
Previous Message Christopher Kings-Lynne 2005-10-17 14:46:40 Re: [GENERAL] Oracle buys Innobase