Horton

Re: Bug #613: Sequence values fall back to previously chec

Tom Lane <tgl@sss.pgh.pa.us>

View thread
From: Tom Lane <tgl@sss.pgh.pa.us>
To: "'Ben Grimm'" <bgrimm@zaeon.com>
Cc: "Vadim Mikheev" <vmikheev@sectorbase.com>, "Tom Pfau" <T.Pfau@emCrit.com>, "Bruce Momjian" <pgman@candle.pha.pa.us>, pgsql-bugs@postgresql.org, pgsql-hackers@postgresql.org
Date: 2002-03-15T16:03:50Z
Lists: pgsql-bugs, pgsql-hackers 
"'Ben Grimm'" <bgrimm@zaeon.com> writes:
> On Fri, 15 Mar 2002, Tom Lane wrote:
>> What's bug #3?  I don't recall a third issue.

> The problem I was seeing before is that when the postmaster was shutdown 
> properly, log_cnt in the sequence record was saved with whatever value it 
> had at the time.

Right, it's supposed to do that.

> So when it loaded from disk it would have a value greater 
> than zero resulting in no XLogInsert until you'd exceded log_cnt calls to
> nextval.  

This is the same as the post-checkpoint issue: we fix it by forcing an
XLogInsert on the first nextval after a checkpoint (or system startup).

			regards, tom lane