Date: Tue, 11 Jun 2024 05:28:45 -0700 (PDT)
From: Rich Shepard <rshepard@appl-ecosys.com>
To: pgsql-general@lists.postgresql.org
Subject: Re: Gaps in PK sequence numbers [RESOLVED]
In-Reply-To: <88E9C97A-E616-4162-9CAB-64C98C5620B6@thebuild.com>
Message-ID: <92fc77dd-8b98-2810-107b-aac4795191d5@appl-ecosys.com>
References: <35fd10ab-5f7f-7a57-9cc5-c03d81476d13@appl-ecosys.com> <DB68A3C3-FCF6-4815-9C5C-A77310B66474@thebuild.com> <f9ab3b2b-508-ddcf-f01c-3c805242ee3@appl-ecosys.com> <88E9C97A-E616-4162-9CAB-64C98C5620B6@thebuild.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed
Archived-At: <https://www.postgresql.org/message-id/92fc77dd-8b98-2810-107b-aac4795191d5%40appl-ecosys.com>
Precedence: bulk

On Mon, 10 Jun 2024, Christophe Pettus wrote:

> The sequence functions are documented here:
> 	https://www.postgresql.org/docs/current/functions-sequence.html
> setval is the function you want. You can use a SELECT so you don't have to
> copy values around:
> 	select setval('t_pk_seq', (select max(pk) from t));
> That form of setval() sets the sequence so that the next value will be one
> more than the value you set it to, so you don't have to do max()+1 there.

Thanks again, Christophe.

Regards,

Rich