Postgres Pro
Downloads
Home   >   mailing lists

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

From Holger Jakobs
Subject Re: nextval() on serial using old, existing value on insert?
Date
Msg-id 8234056e-9d60-2a41-1701-1afb08e330db@jakobs.com
Whole thread Raw
In response to Re: nextval() on serial using old, existing value on insert?  (hubert depesz lubaczewski <depesz@depesz.com>)
Responses Re: nextval() on serial using old, existing value on insert?
List pgsql-admin
Tree view 
Am 11.05.23 um 14:38 schrieb hubert depesz lubaczewski:
> On Wed, May 10, 2023 at 10:06:28PM -0700, Wells Oliver wrote:
>> As a follow up, I've selected max(common_key) from the table and
>> setval()'ed on the sequence to that +1 and I think that should make this go
>> away. Any reason why that's insane?
> If you're on pg 10 or newer, you can make the id to be "generated always
> as identity" which will make it impossible to provide id value from
> user, thus making the problem impossible to happen.
>
> Best regards,
>
> depesz

Impossible to happen by chance. A malicious user could always use 
OVERRIDING SYSTEM VALUE clause.

Kind Regards,

Holger

-- 
Holger Jakobs, Bergisch Gladbach, Tel. +49-178-9759012
Attachment

pgsql-admin by date:

Previous
From: ROHIT SACHDEVA
Date:
Subject: Related To Query Optimization
Next
From: Holger Jakobs
Date:
Subject: Re: Related To Query Optimization