Re: Automatic PK values not added to new rows

From: Thomas Kellerer <shammat(at)gmx(dot)net>
To: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: Automatic PK values not added to new rows
Date: 2022-05-25 19:41:41
Message-ID: 6d67d16b-7cdd-2f40-9ebe-82a499eb11c2@gmx.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Rich Shepard schrieb am 25.05.2022 um 20:15:
> On Wed, 25 May 2022, Adrian Klaver wrote:
>
>> Do:
>> select * from people_person_nbr_seq;
>> and report back the results.
>
> Adrian,
>
> Huh!
> bustrac=# select * from people_person_nbr_seq;
>  last_value | log_cnt | is_called ------------+---------+-----------
>         683 |      32 | t
> (1 row)
>
> It's out of sync with
>  select max(person_nbr) from people;
>
> Is there a way for me to synchronize the two?

If you want to prevent such a situation in the future, you might want to
consider defining those columns as "generated always as identity" instead
of "serial".

Then you'd get an error if you try to bypass the database generated values.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Abhishek Bhola 2022-05-25 22:41:33 Re: PG 13.6 : Data corruption error message not being sent to syslog
Previous Message Rich Shepard 2022-05-25 18:25:10 Re: Automatic PK values not added to new rows [RESOLVED]