Re: Double sequence increase on single insert with RULE on targeted table - Mailing list pgsql-bugs

From tomas@tuxteam.de (Tomas Zerolo)
Subject Re: Double sequence increase on single insert with RULE on targeted table
Date
Msg-id 20051116060227.GB6265@www.trapp.net
Whole thread Raw
In response to Re: Double sequence increase on single insert with RULE on targeted table  (Michael Fuhr <mike@fuhr.org>)
Responses Re: Double sequence increase on single insert with RULE on  (Sarunas Krisciukaitis <sarunask@lonus-tech.com>)
List pgsql-bugs
On Tue, Nov 15, 2005 at 10:51:10PM -0700, Michael Fuhr wrote:
> On Wed, Nov 16, 2005 at 06:29:40AM +0100, Tomas Zerolo wrote:
> > AFAIK, serials are not guaranteed to produce sequential values; tehy
> > will produce unique values. That means that they can (and sometimes
> > will) jump.
>=20
> In this particular case, however, the behavior is due to the rule
> on test1:
>=20
> CREATE RULE test1_on_insert AS ON INSERT TO test1
>   DO INSERT INTO test_log1 (qid) VALUES (new.id);

[...]

Oops, I didn't see that. Your eyes are sharper than mine ;-)

thanks
-- tomas

pgsql-bugs by date:

Previous
From: Michael Fuhr
Date:
Subject: Re: Double sequence increase on single insert with RULE on targeted table
Next
From: Eugene Chow
Date:
Subject: Assigning null to an array element in plpgsql