Postgres Pro
Downloads
Home   >   mailing lists

Re: We've been affected by a pg_upgrade bug. What do we do next? - Mailing list pgsql-general

From Shaun Thomas
Subject Re: We've been affected by a pg_upgrade bug. What do we do next?
Date
Msg-id 0683F5F5A5C7FE419A752A034B4A0B9797AF64F9@sswchi5pmbx2.peak6.net
Whole thread Raw
In response to Re: We've been affected by a pg_upgrade bug. What do we do next?  (Andres Freund <andres@2ndquadrant.com>)
Responses Re: We've been affected by a pg_upgrade bug. What do we do next?
List pgsql-general
Tree view 
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
suchfile 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
ofthat. 

______________________________________________

See http://www.peak6.com/email_disclaimer/ for terms and conditions related to this email

pgsql-general by date:

Previous
From: Andres Freund
Date:
Subject: Re: We've been affected by a pg_upgrade bug. What do we do next?
Next
From: Alvaro Herrera
Date:
Subject: Re: We've been affected by a pg_upgrade bug. What do we do next?