Re: could not open file "pg_clog/0BFF"

http://svr5.postgresql.org/pgsql-hackers/2006-03/msg01198.php
http://www.mail-archive.com/pgsql-general(at)postgresql(dot)org/msg90845.html

This is related to an autovacuum bug and the freeze logic with
template0....and probably a corrupted pg_statistics table in template0....
you should upgrade AND repair the template0 issue (I actually replaced
template0 with a copy from a replicant database)
......But take heed, if you don't 'do' something about it, autovacuum is
actually stopping with tempate 0 and never getting to the rest of your
database (as I found out)

Patrick Lindeman wrote:
> What could have caused the error "could not access status of transaction
> 3221180546" and is it more than just coincidence that since that moment
> the vacuum stopped running?
>
> Is there anything we can do to prevent this in future use?
>
> Besides we are using PostgreSQL 8.1.3.
>
> Any help would be appreciated.
>
> Regards,
> Patrick Lindeman
>
> ---------------------------(end of broadcast)---------------------------
> TIP 9: In versions below 8.0, the planner will ignore your desire to
> choose an index scan if your joining column's datatypes do not
> match
>