From: | Steve Crawford <scrawford(at)pinpointresearch(dot)com> |
---|---|
To: | Jean-Christophe Roux <jcxxr(at)yahoo(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Sequence skipping values |
Date: | 2006-02-10 17:57:31 |
Message-ID: | 43ECD40B.6040005@pinpointresearch.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Jean-Christophe Roux wrote:
> Hello,
> I have a table with and id field (primary key) which default value is
> the result of a sequence (increment explicitly set to 1).
> To my surprise, the real increment on insert is the total number of rows
> of the table. For instance, with 41 rows and a sequence last_value of
> 1141, the next insert row will have a value of 1182. It is not a big
> problem but I don't like skipping and wasting values in a sequence.
> Also, I'd like to understand what's going on!
> If someone could give me a clue that wold be greatly appreciated
> thanks
> JC
Any rules, triggers, etc. involved? How are the inserts done (insert one
record into the table)? What relationships does the table have to any
other tables? Anything else accessing that sequence?
There is no guarantee that a sequence will be contiguous. For example,
begin...insert into...rollback will not reset the sequence as other
transactions could have incremented the sequence.
Cheers,
Steve
From | Date | Subject | |
---|---|---|---|
Next Message | David Rio Deiros | 2006-02-10 17:59:14 | Re: distinct not working in a multiple join |
Previous Message | Scott Marlowe | 2006-02-10 17:53:33 | Re: Sequence skipping values |