Jaime Casanova <systemguards@gmail.com> writes:

> The only problem i have found until now is that
> update v_foo set col1 = DEFAULT; execute nextval twice per every record.
> so there will be a gasp between numbers, but AFAIK nextval has no guarantee
> of returning sequential numbers.

While there's no guarantee that strong there's still an expected behaviour.
sequences generate sequential numbers and only skip in specific cases.

I think this would still surprise and bother most users.

--
greg


---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faq

On 28 May 2005 10:25:48 -0400, Greg Stark <gsstark@mit.edu> wrote:
>
> Jaime Casanova <systemguards@gmail.com> writes:
>
> > The only problem i have found until now is that
> > update v_foo set col1 = DEFAULT; execute nextval twice per every record.
> > so there will be a gasp between numbers, but AFAIK nextval has no
> guarantee
> > of returning sequential numbers.
>
> While there's no guarantee that strong there's still an expected behaviour.
> sequences generate sequential numbers and only skip in specific cases.
>
> I think this would still surprise and bother most users.
>
Certainly, i will look deeper in it.

--
regards,
Jaime Casanova
(DBA: DataBase Aniquilator

---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faq