Re: 'SGT DETAIL: Could not open file "pg_clog/05DC": No such file or directory' - what to do now?

Tomasz Chmielewski <mangoo@wpkg.org> wrote:

> This repeated many times:
>
> /var/log/postgresql/postgresql_log.1:May  3 18:24:49 db10
> postgres[21363]: [26999-1] 2011-05-03 18:24:49 SGT ERROR:  could
> not access status of transaction 1573786613
> /var/log/postgresql/postgresql_log.1-May  3 18:24:49 db10
< postgres[21363]: [26999-2] 2011-05-03 18:24:49 SGT DETAIL:  Could
> not open file "pg_clog/05DC": No such file or directory.
> /var/log/postgresql/postgresql_log.1-May  3 18:24:49 db10
> postgres[21363]: [26999-3] 2011-05-03 18:24:49 SGT STATEMENT:
> SELECT 1 FROM core_wot_seq FOR UPDATE
>
>
> Today I have this:
>
> /var/log/postgresql/postgresql_log:May  4 22:43:44 db10
> postgres[15773]: [555-1] 2011-05-04 22:43:44 SGT ERROR:  could not
> access status of transaction 1612337841
> /var/log/postgresql/postgresql_log-May  4 22:43:44 db10
> postgres[15773]: [555-2] 2011-05-04 22:43:44 SGT DETAIL:  Could
> not open file "pg_clog/0601": No such file or directory.
> /var/log/postgresql/postgresql_log-May  4 22:43:44 db10
> postgres[15773]: [555-3] 2011-05-04 22:43:44 SGT STATEMENT:
> SELECT 1 FROM core_wbl_seq FOR UPDATE
>
> Only such two (different) occurrences; repeated 10-20 times; two
> different tables.

> how should I best recover from this?

If you hadn't already said you were running on 8.3.14 I would have
wondered whether you had used pg_migrator/pg_upgrade.  As it is, I'm
going to admit I'm out of my depth and hope someone else jumps in
here.

-Kevin