Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtps  (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.94.2)
	(envelope-from <pgsql-general-owner+archive@lists.postgresql.org>)
	id 1sHrlE-00BH5u-Vx
	for pgsql-general@arkaria.postgresql.org; Thu, 13 Jun 2024 21:13:32 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.94.2)
	(envelope-from <pgsql-general-owner+archive@lists.postgresql.org>)
	id 1sHrlC-0081wf-5t
	for pgsql-general@arkaria.postgresql.org; Thu, 13 Jun 2024 21:13:31 +0000
Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29])
	by malur.postgresql.org with esmtps  (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.94.2)
	(envelope-from <rshepard@appl-ecosys.com>)
	id 1sHrlB-0081wX-Qq
	for pgsql-general@lists.postgresql.org; Thu, 13 Jun 2024 21:13:30 +0000
Received: from mail.appl-ecosys.com ([50.126.108.78])
	by magus.postgresql.org with esmtps  (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.94.2)
	(envelope-from <rshepard@appl-ecosys.com>)
	id 1sHrlA-001Wop-9I
	for pgsql-general@lists.postgresql.org; Thu, 13 Jun 2024 21:13:30 +0000
Received: from salmo.appl-ecosys.com (salmo.appl-ecosys.com [192.168.55.1])
	by mail.appl-ecosys.com (Postfix) with ESMTP id 0E65D2A2B7C
	for <pgsql-general@lists.postgresql.org>; Thu, 13 Jun 2024 14:13:26 -0700 (PDT)
Date: Thu, 13 Jun 2024 14:13:26 -0700 (PDT)
From: Rich Shepard <rshepard@appl-ecosys.com>
To: pgsql-general@lists.postgresql.org
Subject: Re: Reset sequence to current maximum value of rows
In-Reply-To: <CAM8SmLUzKLyS6sahhGZZn2cgRQ6jzHJ6ynRHLm6AcSapWMvjSA@mail.gmail.com>
Message-ID: <1a214ab-b1b8-83a5-ea62-a1a07341fc53@appl-ecosys.com>
References: <387fa6c2-5de-f24-d522-46282597703@appl-ecosys.com> <CANzqJaAavydD4XMgkXRUQ_=aAFOGBMVBCKfeB0PnhrZrAWbgng@mail.gmail.com> <c141507f-a21-65dd-55fa-bd9bad7b9fe4@appl-ecosys.com> <CANzqJaB0OeAchVgnTznmPTbo9Y-H9r9g7S=TqJb25eX_KodcRA@mail.gmail.com>
 <bcf7b38-857e-b44c-a0c5-71bfc1f52b9c@appl-ecosys.com> <CAM8SmLUzKLyS6sahhGZZn2cgRQ6jzHJ6ynRHLm6AcSapWMvjSA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset=US-ASCII
List-Id: <pgsql-general.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-general@lists.postgresql.org>
List-Owner: <mailto:pgsql-general-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-general>
Archived-At: <https://www.postgresql.org/message-id/1a214ab-b1b8-83a5-ea62-a1a07341fc53%40appl-ecosys.com>
Precedence: bulk

On Thu, 13 Jun 2024, Jeremy Smith wrote:

> There's no need to specify the column if it has a default value, but
> specifying it did not cause the issue that you saw.

Jeremy,

I did not know this. While the reason for the issue shall remain unknown, it
did happen and my update script restored order to the table.

Thanks,

Rich