Re: [GENERAL] could not access status of transaction 1118722281

2011-04-09 Thread Gordon Shannon
Turns out this was most likely the pg_upgrade bug. In our case, I was able to dump and recreate the table in question. Since then, this has been made public: http://wiki.postgresql.org/wiki/20110408pg_upgrade_fix -- View this message in context:

[GENERAL] could not access status of transaction 1118722281

2011-04-04 Thread Gordon Shannon
Running 9.0.2 on Centos. I just discovered this in my production error log. Starting about 45 minutes ago, I got 70 of these, within 2 seconds: 28652 2011-04-04 21:47:29 EDT [33]WARNING: PD_ALL_VISIBLE flag was incorrectly set in relation pg_toast_49338181 page 16820 These warnings were

[GENERAL] could not access status of transaction 825832753

2009-12-07 Thread Stephen Tyler
I just got this error, and I don't know why I got it: 7/12/09 2:57:24 PMorg.postgresql.postgres[89]ERROR: could not access status of transaction 825832753 7/12/09 2:57:24 PMorg.postgresql.postgres[89]DETAIL: Could not open file pg_clog/0313: No such file or directory. 7/12/09

[GENERAL] could not access status of transaction

2009-03-25 Thread Tom Duffey
Hi All, One of our databases suffered a problem yesterday during a normal update, something we have been doing for years. Near the end of the process a foreign key constraint is rebuilt on a table containing several hundred million rows. Rebuilding the constraint failed with the

Re: [GENERAL] could not access status of transaction

2009-03-25 Thread Tom Lane
Tom Duffey tduf...@techbydesign.com writes: One of our databases suffered a problem yesterday during a normal update, something we have been doing for years. Near the end of the process a foreign key constraint is rebuilt on a table containing several hundred million rows. Rebuilding

Re: [GENERAL] could not access status of transaction

2009-03-25 Thread Tom Duffey
Hi Tom, On Mar 25, 2009, at 9:02 PM, Tom Lane wrote: Tom Duffey tduf...@techbydesign.com writes: One of our databases suffered a problem yesterday during a normal update, something we have been doing for years. Near the end of the process a foreign key constraint is rebuilt on a table

[GENERAL] could not access status of transaction 4244329

2004-10-13 Thread [EMAIL PROTECTED]
Hi: I've migrated a couple of weeks ago from 7.4.2 to 7.4.5 and I am getting this error after executing a query: Warning: pg_exec() query failed: ERROR: could not access status of transaction 4244329 in /home/wisconsin/www/_proc/bbdd/_c_bbdd.php on line 160 ERROR ACCESO BASE DE DATOSERROR:

Re: [GENERAL] could not access status of transaction 4244329

2004-10-13 Thread Gaetano Mendola
[EMAIL PROTECTED] wrote: Hi: I've migrated a couple of weeks ago from 7.4.2 to 7.4.5 and I am getting this error after executing a query: Warning: pg_exec() query failed: ERROR: could not access status of transaction 4244329 in /home/wisconsin/www/_proc/bbdd/_c_bbdd.php on line 160 ERROR

Re: [GENERAL] could not access status of transaction 4244329

2004-10-13 Thread Tom Lane
[EMAIL PROTECTED] [EMAIL PROTECTED] writes: ERROR: could not access status of transaction 4244329 DETAIL: could not open file /usr/local/pgsql/data/pg_clog/0004: No existe el fichero o el directorio What files actually appear in /usr/local/pgsql/data/pg_clog/ ? The standard advice