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

From Michael Fuhr
Subject Re: Double sequence increase on single insert with RULE on targeted table
Date
Msg-id 20051116055110.GA59914@winnie.fuhr.org
Whole thread Raw
In response to Re: Double sequence increase on single insert with RULE on targeted table  (tomas@tuxteam.de (Tomas Zerolo))
Responses Re: Double sequence increase on single insert with RULE on targeted table  (tomas@tuxteam.de (Tomas Zerolo))
List pgsql-bugs
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.

In this particular case, however, the behavior is due to the rule
on test1:

CREATE RULE test1_on_insert AS ON INSERT TO test1
  DO INSERT INTO test_log1 (qid) VALUES (new.id);

This "gotcha" comes up occasionally; it's due to the fact that rules
are macros.  Search the archives for past discussion.

--
Michael Fuhr

pgsql-bugs by date:

Previous
From: tomas@tuxteam.de (Tomas Zerolo)
Date:
Subject: Re: Double sequence increase on single insert with RULE on targeted table
Next
From: tomas@tuxteam.de (Tomas Zerolo)
Date:
Subject: Re: Double sequence increase on single insert with RULE on targeted table