Re: Bug #613: Sequence values fall back to previously chec - Mailing list pgsql-bugs

From Tom Lane
Subject Re: Bug #613: Sequence values fall back to previously chec
Date
Msg-id 20877.1016202876@sss.pgh.pa.us
Whole thread Raw
In response to Re: Bug #613: Sequence values fall back to previously chec  ("'Ben Grimm'" <bgrimm@zaeon.com>)
Responses Re: Bug #613: Sequence values fall back to previously chec  ("'Ben Grimm'" <bgrimm@zaeon.com>)
List pgsql-bugs
"'Ben Grimm'" <bgrimm@zaeon.com> writes:
> When these bugs are fixed there is still the issue of bug #3 that I 
> came across.  The one that I work around by resetting log_cnt to 0 when a 
> backend initializes a sequence.  It's this third bug that made the other 
> two so apparent.  Fixing them does not obviate the need to fix this one.

What's bug #3?  I don't recall a third issue.
        regards, tom lane


pgsql-bugs by date:

Previous
From: pgsql-bugs@postgresql.org
Date:
Subject: Bug #620: create index ... (date_part('year', d)) fails
Next
From: Tom Lane
Date:
Subject: Re: Bug #613: Sequence values fall back to previously chec