"'Ben Grimm'" <bgrimm(at)zaeon(dot)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
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
In response to
pgsql-hackers by date
|Next:||From: Thomas Lockhart||Date: 2002-03-15 16:19:15|
|Subject: Re: timestamp_part() bug?|
|Previous:||From: 'Ben Grimm'||Date: 2002-03-15 15:44:35|
|Subject: Re: Bug #613: Sequence values fall back to previously chec|
pgsql-bugs by date
|Next:||From: Peter Eisentraut||Date: 2002-03-15 16:21:27|
|Subject: Re: Bug #617: In SQL the tableowner is not allowed|
|Previous:||From: Thomas Lockhart||Date: 2002-03-15 15:47:32|
|Subject: Re: Bug #614: Incorrect parse with time function|