From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | bgrimm(at)zaeon(dot)com, pgsql-bugs(at)postgresql(dot)org, Vadim Mikheev <vmikheev(at)sectorbase(dot)com> |
Subject: | Re: Bug #613: Sequence values fall back to previously checkpointed |
Date: | 2002-03-12 23:36:15 |
Message-ID: | 5565.1015976175@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> bgrimm(at)zaeon(dot)com wrote:
>> the sequence again. Kill -9 the postmaster. Tried to insert into the
>> table, but to no avail... duplicate key. currval of the sequence and
>> it matched the value right after the checkpoint. I've been able to
>> duplicate that scenario several times.
> I just tested it here by doing a similar test of several nextval()
> calls, but then doing an INSERT and kill, and on restart, the sequence
> counter did have the proper value.
There have been prior reports of similar problems --- all quite
unrepeatable in my testing, and despite considerable study of the source
code I can't see how it could happen. A reproducible test case would be
a tremendous help.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2002-03-12 23:46:51 | Re: Bug #613: Sequence values fall back to previously checkpointed |
Previous Message | Bruce Momjian | 2002-03-12 22:49:26 | Re: Bug #613: Sequence values fall back to previously checkpointed |