| From: | Shaun Thomas <sthomas(at)optionshouse(dot)com> |
|---|---|
| To: | 'Andres Freund' <andres(at)2ndquadrant(dot)com> |
| Cc: | 'Adrian Klaver' <adrian(dot)klaver(at)aklaver(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: We've been affected by a pg_upgrade bug. What do we do next? |
| Date: | 2014-07-16 15:15:53 |
| Message-ID: | 0683F5F5A5C7FE419A752A034B4A0B9797AF64F9@sswchi5pmbx2.peak6.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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.
______________________________________________
See http://www.peak6.com/email_disclaimer/ for terms and conditions related to this email
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2014-07-16 15:22:54 | Re: We've been affected by a pg_upgrade bug. What do we do next? |
| Previous Message | Andres Freund | 2014-07-16 15:12:22 | Re: We've been affected by a pg_upgrade bug. What do we do next? |