Postgres Pro
Downloads
Home   >   mailing lists

Re: nextval() on serial using old, existing value on insert? - Mailing list pgsql-admin

From David G. Johnston
Subject Re: nextval() on serial using old, existing value on insert?
Date
Msg-id CAKFQuwaV9z4xUoxaqLx0_-7UjaafWX3O0=1Rsu4EDi87PTxUrQ@mail.gmail.com
Whole thread Raw
In response to nextval() on serial using old, existing value on insert?  (Wells Oliver <wells.oliver@gmail.com>)
Responses Re: nextval() on serial using old, existing value on insert?
List pgsql-admin
Tree view

On Wednesday, May 10, 2023, Wells Oliver <wells.oliver@gmail.com> wrote:
I have a simple table with a given column defined like so:

 common_key    | integer |           | not null | nextval('alias.identity_common_key_seq'::regclass)  | plain


Very very very infrequently, on an INSERT where this column is not specified, this column will be assigned a value that already exists in the table, versus the next presumably unused value in the sequence. I cannot figure this out. Is there any reason why this might be the case?

Most likely someone inserted data without using the sequence and eventually the sequence catches up with that previously inserted data.

David J.
 

pgsql-admin by date:

Previous
From: Keith
Date:
Subject: Re: nextval() on serial using old, existing value on insert?
Next
From: Wells Oliver
Date:
Subject: Re: nextval() on serial using old, existing value on insert?