Re: Gaps in PK sequence numbers

From: Rich Shepard <rshepard(at)appl-ecosys(dot)com>
To: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: Gaps in PK sequence numbers
Date: 2024-06-11 01:13:55
Message-ID: d44076fc-fcd7-445c-da76-5d87c7d2dc4@appl-ecosys.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Mon, 10 Jun 2024, David G. Johnston wrote:

> For efficiency the only thing used to determine the next value of a
> sequence is the stored value of the last sequence value issued. Where that
> value may have been used, in a table as a PK or some other purpose, does
> not enter into it. Using a sequence as a default does indeed become
> problematic if you don't use it exclusively. If you do use it exclusively
> usually you just set the last value to be the maximum needed and use it
> going forward. The numbers from deleted rows simply remain missing in the
> table.

David,

Thanks for the explanation. I had entered PKs without using the sequence.

Regards,

Rich

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Christophe Pettus 2024-06-11 01:21:59 Re: Gaps in PK sequence numbers [RESOLVED]
Previous Message Rich Shepard 2024-06-11 01:10:49 Re: Gaps in PK sequence numbers [RESOLVED]