Re: [GENERAL] 20110408pg_upgrade_fix and 'FATAL: could not access status of transaction...'

Resolved the startup problem by identifying which pg_clog file it was failing on with: strace postgres --single -D 9.0/data Then grabbed that file from the replication slave. Cheers h -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: h

Re: [GENERAL] 20110408pg_upgrade_fix and 'FATAL: could not access status of transaction...'

I managed to resolve this issue. Using strace -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general

Re: [GENERAL] 20110408pg_upgrade_fix and 'FATAL: could not access status of transaction...'

On Sat, April 23, 2011 09:56, Henry C. wrote: > 1. how to proceed with getting db1 back up so I can run the script? > 2. how to proceed with replicated database (db2)? (switch to standalone > (since it's in readonly replication mode) and run upgrade fix script as per > wiki, or leave as-is...) R

[GENERAL] 20110408pg_upgrade_fix and "FATAL: could not access status of transaction..."

Hi, Lovely start to Saturday morning. My eyes are misting over with joy. I'm trying to figure out whether I'm affected (probably) by this beauty http://wiki.postgresql.org/wiki/20110408pg_upgrade_fix (I missed the ANNOUNCE advisory, even more joy). One of my DBs fails at startup: 2011-04-23 09: