Thread: ...
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
What are the most popular cars? Find out at Yahoo! Autos
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
What are the most popular cars? Find out at Yahoo! Autos
try using CACHE 1 (which is default) in the sequence defintion. http://www.postgresql.org/docs/8.1/static/sql-createsequence.html On 2/10/06, Jean-Christophe Roux <jcxxr@yahoo.com> 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 > > > > ________________________________ > > What are the most popular cars? Find out at Yahoo! Autos > >