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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "'Ben Grimm'" <bgrimm(at)zaeon(dot)com>
Cc: "Vadim Mikheev" <vmikheev(at)sectorbase(dot)com>, "Tom Pfau" <T(dot)Pfau(at)emCrit(dot)com>, "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us>, pgsql-bugs(at)postgresql(dot)org, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Bug #613: Sequence values fall back to previously chec
Date: 2002-03-15 16:03:50
Message-ID: 21303.1016208230@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

"'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
> 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

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Peter Eisentraut 2002-03-15 16:21:27 Re: Bug #617: In SQL the tableowner is not allowed
Previous Message Thomas Lockhart 2002-03-15 15:47:32 Re: Bug #614: Incorrect parse with time function

Browse pgsql-hackers by date

  From Date Subject
Next Message Thomas Lockhart 2002-03-15 16:19:15 Re: timestamp_part() bug?
Previous Message 'Ben Grimm' 2002-03-15 15:44:35 Re: Bug #613: Sequence values fall back to previously chec