| From: | Jaime Casanova <systemguards(at)gmail(dot)com> |
|---|---|
| To: | Greg Stark <gsstark(at)mit(dot)edu> |
| Cc: | Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: thw rewriter and default values, again |
| Date: | 2005-05-28 16:38:43 |
| Message-ID: | c2d9e70e05052809383dcb516d@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 28 May 2005 10:25:48 -0400, Greg Stark <gsstark(at)mit(dot)edu> wrote:
>
> Jaime Casanova <systemguards(at)gmail(dot)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 ;)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2005-05-28 16:46:29 | Re: unsafe use of hash_search(... HASH_ENTER ...) |
| Previous Message | Jaime Casanova | 2005-05-28 16:36:46 | Re: thw rewriter and default values, again |