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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Mikheev, Vadim" <vmikheev(at)SECTORBASE(dot)COM>
Cc: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, bgrimm(at)zaeon(dot)com, pgsql-bugs(at)postgresql(dot)org, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Bug #613: Sequence values fall back to previously chec kpointed
Date: 2002-03-13 22:29:08
Message-ID: 11823.1016058548@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

I said:
> Mmm ... maybe. Is this safe if a checkpoint is currently in progress?
> Seems like you could look at RedoRecPtr and decide you are okay, but you
> really are not if checkpointer has already dumped sequence' disk
> buffer and will later set RedoRecPtr to a value beyond the old LSN.

Oh, wait, I take that back: the checkpointer advances RedoRecPtr
*before* it starts to dump disk buffers.

I'm still worried about whether we shouldn't try to simplify, rather
than add complexity.

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Ben Grimm 2002-03-13 22:32:28 Re: Bug #613: Sequence values fall back to previously checkpointed
Previous Message Tom Lane 2002-03-13 22:00:56 Re: Bug #613: Sequence values fall back to previously chec kpointed

Browse pgsql-hackers by date

  From Date Subject
Next Message Mikheev, Vadim 2002-03-13 22:34:41 Re: Bug #613: Sequence values fall back to previously chec
Previous Message Ian Barwick 2002-03-13 22:23:08 Re: Archives