| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Wells Oliver <wells(dot)oliver(at)gmail(dot)com> |
| Cc: | pgsql-admin <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: nextval() on serial using old, existing value on insert? |
| Date: | 2023-05-11 04:55:12 |
| Message-ID: | CAKFQuwaV9z4xUoxaqLx0_-7UjaafWX3O0=1Rsu4EDi87PTxUrQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Wednesday, May 10, 2023, Wells Oliver <wells(dot)oliver(at)gmail(dot)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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Wells Oliver | 2023-05-11 05:02:51 | Re: nextval() on serial using old, existing value on insert? |
| Previous Message | Keith | 2023-05-11 04:54:09 | Re: nextval() on serial using old, existing value on insert? |