Re: BUG #5976: Corrupted pages on the production database

From: Vlad Arkhipov <arhipov(at)dc(dot)baikal(dot)ru>
To: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #5976: Corrupted pages on the production database
Date: 2011-04-13 13:07:29
Message-ID: 4DA5A011.4030007@dc.baikal.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

13.04.2011 20:48, Kevin Grittner wrote:
> "Vlad Arkhipov" wrote:
>
>
>> PostgreSQL version: 9.0.3
>>
>
>
>> pg_dump: SQL command failed
>> pg_dump: Error message from server: ERROR: could not access status
>> of transaction 3499806839
>> DETAIL: Could not open file "pg_clog/0D09": No such file or
>> directory.
>>
>
> Did you get to 9.0 using pg_upgrade?
>
> http://archives.postgresql.org/pgsql-announce/2011-04/msg00007.php
>
> -Kevin
>
>
No. We have upgraded to 9.0 several months ago and daily pg_dump worked
well until 10 April 2011. Also the corrupted table truncates and filled
with data every hour, so pg_upgrade could not affect it.

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Merlin Moncure 2011-04-13 13:42:00 Re: [GENERAL] PostgreSQL backend process high memory usage issue
Previous Message Kevin Grittner 2011-04-13 11:48:43 Re: BUG #5976: Corrupted pages on the production database