| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "George Pavlov" <gpavlov(at)mynewplace(dot)com> |
| Cc: | "PostgreSQL general" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: apparent wraparound |
| Date: | 2006-11-11 00:06:14 |
| Message-ID: | 7619.1163203574@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
"George Pavlov" <gpavlov(at)mynewplace(dot)com> writes:
> I am on 8.1.3 on Linux. I have a
> log entry like this:
> 2006-11-08 12:38:34 PST [3739]: [3-1] LOG: could not truncate directory
> "pg_multixact/members": apparent wraparound
During crash recovery? If so, probably nothing to worry about, per this
8.1.5 bug fix:
2006-07-19 20:46 tgl
* src/backend/access/transam/multixact.c (REL8_1_STABLE): Don't try
to truncate multixact SLRU files in checkpoints done during xlog
recovery. In the first place, it doesn't work because slru's
latest_page_number isn't set up yet (this is why we've been hearing
reports of strange "apparent wraparound" log messages during crash
recovery, but only from people who'd managed to advance their
next-mxact counters some considerable distance from 0). In the
second place, it seems a bit unwise to be throwing away data during
crash recovery anwyway. This latter consideration convinces me to
just disable truncation during recovery, rather than computing
latest_page_number and pushing ahead.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | George Pavlov | 2006-11-11 00:12:35 | Re: apparent wraparound |
| Previous Message | Lars Heidieker | 2006-11-11 00:00:29 | Re: FK pointing to a VIEW |