On 2/6/07, Stefan Kaltenbrunner <stefan@xxxxxxxxxxxxxxxx> wrote:
Merlin Moncure wrote: > On 2/6/07, Merlin Moncure <mmoncure@xxxxxxxxx> wrote: >> around 6:30 this morning, I started getting the following messages in >> my log: >> >> Feb 6 06:33:34 mojo postgres[1117]: [2-1] :: ERROR: could not access >> status of transaction 544441911 >> Feb 6 06:34:35 mojo postgres[1128]: [2-1] :: ERROR: could not access >> status of transaction 544441911 >> [...] >> >> repeated roughly once a minute. I've never seen this before. this is >> on postgres 8.1.1 running on fedora core 4 smp. I don't have any >> contextual information yet but I'm getting ready to turn statement >> logging on. >> >> Anybody know what this is? > [x-posting to -hackers] > > actually, here is some more relevant bits from the log. > Feb 6 06:31:33 mojo postgres[1088]: [1-1] :: LOG: autovacuum: > processing database "template0" > Feb 6 06:31:33 mojo postgres[1088]: [2-1] :: ERROR: could not access > status of transaction 544441911 > Feb 6 06:31:33 mojo postgres[1088]: [2-2] :: DETAIL: could not open > file "pg_clog/0207": No such file or directory hmm I first thought it could have been http://archives.postgresql.org/pgsql-committers/2006-01/msg00288.php which affects 8.1.1 but that's not the very same error as the one created by the above bug.
ya, it doesn't seem to match, as this seems to be repeating quite regularly. interesting that my 'clog' files start at 06B6 and count up. 0207 is way off the charts. a lot of applications are hitting this database, and so far everything seems to be running ok (i found this log msg by accident), but I am now officially very nervous. merlin
