From: Stevie <stevieg@web.de>
To: pgsql-admin <pgsql-admin@postgresql.org>
Subject: Re: ERROR: could not access status of transaction
Date: Fri, 25 Mar 2011 09:50:04 +0100
Message-ID: <1301043004.2357.8.camel@stevie> (raw)
In-Reply-To: <AANLkTims48njGKkvkXHiTG6=19hQ31VFmFRPPLg+5w03@mail.gmail.com>
References: <1300970362.2349.27.camel@stevie>
<AANLkTims48njGKkvkXHiTG6=19hQ31VFmFRPPLg+5w03@mail.gmail.com>
Hello
> There is a commit log corruption in your database.
Yes, and it seems this is produce by a pg_upgrade bug from pg8 to pg9 in
October 2010.
> You need to make the files with right size (256K of zeroes).A suitable
> "dd" from /dev/zero will accomplish this on modernUnixen (ie, anything
> that has /dev/zero). Filling of those files with zeroes nothing but "
> all those old transactions are aborted".
I was able to restore these files from backup. The dump is finished
without errors.
This corruption is just on our master replication, which was upgraded.
Is it a good idea to restore the clog files there too?
Regards
Steffen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: stevieg@web.de
Subject: Re: ERROR: could not access status of transaction
In-Reply-To: <1301043004.2357.8.camel@stevie>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox