> 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
> 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
This corruption is just on our master replication, which was upgraded.
Is it a good idea to restore the clog files there too?
In response to
pgsql-admin by date
|Next:||From: Simon Riggs||Date: 2011-03-25 09:42:46|
|Subject: Re: ERROR: could not access status of transaction|
|Previous:||From: Yandong.Yao||Date: 2011-03-25 02:18:00|
|Subject: Re: What does error "psql: Kerberos 5 authentication not