Re: pg_upgrade bug found!

Hi Stephen,

On Fri, Apr 8, 2011 at 6:57 PM, Stephen Frost <sfrost(at)snowman(dot)net> wrote:
> bricklen,
>
> * bricklen (bricklen(at)gmail(dot)com) wrote:
>> I've been noticing in my logs for the past few days the message you
>> note in the wiki. It seems to occur during a vacuum around 7:30am
>> every day. I will be running the suggested script shortly, but can
>> anyone tell me in how bad of shape my db is in? This is our production
>> db with two hot standby's running off it.
>
> Unfortunately, I don't think the script that Bruce posted will help if
> the clog files have been removed (which appears to be the case here).
> Do you have a backup which includes older files which existed under the
> 'pg_clog' directory under your database's root?  Hopefully you do and
> can restore those and restart the database.  If you restore and then
> restart then Bruce's script could be run and hopefully would clear out
> these errors.
>
> Bruce, please correct me if I got any part of this wrong.
>
>        Thanks,
>
>                Stephen

I looked deeper into our backup archives, and it appears that I do
have the clog file reference in the error message "DETAIL: Could not
open file "pg_clog/04BE": No such file or directory."

It exists in an untouched backup directory that I originally made when
I set up the backup and ran pg_upgrade. I'm not sure if it is from
version 8.4 or 9.0.2 though. Is it safe to just copy it into my
production pg_clog dir and restart?