| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Reece Hart <hart(dot)reece(at)gene(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
| Subject: | Re: apparent wraparound |
| Date: | 2006-07-20 00:49:19 |
| Message-ID: | 17811.1153356559@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
I wrote:
> Reece Hart <hart(dot)reece(at)gene(dot)com> writes:
>> After a system crash, postgresql 8.1.4 restarted but reported that I
>> have an apparent wraparound:
>> 2006-07-13 14:03:40 PDT [10092] LOG: could not truncate directory "pg_multixact/offsets": apparent wraparound
>> 2006-07-13 14:03:40 PDT [10092] LOG: could not truncate directory "pg_multixact/members": apparent wraparound
> [ looks at code... ] I wonder if this is happening because
> shared->latest_page_number hasn't been set up yet when we do the
> end-of-recovery checkpoint.
Indeed, I was able to reproduce this after advancing the next-mxact
counters far enough. The consequences seem only cosmetic (ie, a scary
log message during recovery), but still worth fixing. I committed a
patch in HEAD and 8.1.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | lynnsettle@yahoo.com | 2006-07-20 01:17:16 | Re: customizing pg_dump together with copy.c's DoCopy function |
| Previous Message | Paul S | 2006-07-20 00:22:38 | Re: Difference between function and procedure? |