Re: apparent wraparound - Mailing list pgsql-general

From Tom Lane
Subject Re: apparent wraparound
Date
Msg-id 17811.1153356559@sss.pgh.pa.us
Whole thread Raw
In response to Re: apparent wraparound  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Problem getting postmaster PID in pg_regress  (Eric E <whalesuit@gmail.com>)
List pgsql-general
I wrote:
> Reece Hart <hart.reece@gene.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

pgsql-general by date:

Previous
From: "Paul S"
Date:
Subject: Re: Difference between function and procedure?
Next
From: "Merlin Moncure"
Date:
Subject: Re: Linking Tables from 2 databases