Skip site navigation (1) Skip section navigation (2)

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 (view raw or flat)
Thread:
Lists: pgsql-bugspgsql-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

pgsql-hackers by date

Next:From: Thomas LockhartDate: 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 EisentrautDate: 2002-03-15 16:21:27
Subject: Re: Bug #617: In SQL the tableowner is not allowed
Previous:From: Thomas LockhartDate: 2002-03-15 15:47:32
Subject: Re: Bug #614: Incorrect parse with time function

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group