Content-Type: text/plain;
	charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.600.62\))
Subject: Re: Gaps in PK sequence numbers [RESOLVED]
From: Christophe Pettus <xof@thebuild.com>
In-Reply-To: <f9ab3b2b-508-ddcf-f01c-3c805242ee3@appl-ecosys.com>
Date: Mon, 10 Jun 2024 18:21:59 -0700
Cc: pgsql-general@lists.postgresql.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <88E9C97A-E616-4162-9CAB-64C98C5620B6@thebuild.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>
To: Rich Shepard <rshepard@appl-ecosys.com>
Archived-At: <https://www.postgresql.org/message-id/88E9C97A-E616-4162-9CAB-64C98C5620B6%40thebuild.com>
Precedence: bulk


> On Jun 10, 2024, at 18:10, Rich Shepard <rshepard@appl-ecosys.com> =
wrote:
> Thanks, Christophe. Is there a way to reset the sequence to the =
maximum
> number +1? I don't recall seeing this in the postgres docs but will =
look
> again.

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.=