| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Shaun Thomas <sthomas(at)optionshouse(dot)com> |
| Cc: | 'Andres Freund' <andres(at)2ndquadrant(dot)com>, '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:29:16 |
| Message-ID: | 20140716152916.GH11811@eldon.alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Alvaro Herrera wrote:
> 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.
BTW if you do a hexdump of the 0000 file, it should be all zeroes.
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2014-07-16 15:30:36 | Re: We've been affected by a pg_upgrade bug. What do we do next? |
| Previous Message | Shaun Thomas | 2014-07-16 15:27:29 | Re: We've been affected by a pg_upgrade bug. What do we do next? |