Search Postgresql Archives

Re: We've been affected by a pg_upgrade bug. What do we do next?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Shaun Thomas wrote:
> This:
> 
> 23334|4293964274||||53c68b69.5b26|2014-07-16 09:25:45 CDT|ERROR:  could not access status of transaction 7150346
> 23334|4293964274||||53c68b69.5b26|2014-07-16 09:25:45 CDT|DETAIL:  Could not open file "pg_multixact/offsets/006D": No such file or directory.
> 
> Been doing it every ten seconds since yesterday.
> 
> My log line prefix is this:
> 
> log_line_prefix = '%p|%x|%u|%d|%r|%c|%t|'
> 
> So the user, database, and connection source are all blank. The PID is different every time, too. Not sure what to make of that.

It's an autovacuum worker, which is expected.  Just get rid of the 0000
file and all should be well.

-- 
Álvaro Herrera                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services



[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux