public inbox for [email protected]  

help / color / mirror / Atom feed
From: David G. Johnston <[email protected]>
To: Rich Shepard <[email protected]>
Cc: [email protected]
Subject: Re: Reset sequence to current maximum value of rows
Date: Thu, 13 Jun 2024 15:29:01 -0700
Message-ID: <CAKFQuwY-E_EuCHO+Q1o2Lc1d0r-TUp9f18UWRx1TtMEsLzDHvA@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<CAKFQuwba=vb16vR47W0oo3SirkJ+UqLEg5j9-fqe+vm=0Q7_qw@mail.gmail.com>
	<[email protected]>
	<CAKFQuwY4PXdUYWxWzZ+idD64GLA2vrKf_UDcSPf=5VuYSDNRUA@mail.gmail.com>
	<[email protected]>
	<[email protected]>
	<[email protected]>

On Thu, Jun 13, 2024 at 3:13 PM Rich Shepard <[email protected]>
wrote:

> Yes, I'm sure. Early yesterday I did get duplicate key errors. That's when
> I
> looked on stackexchange to learn how to reset the sequence's max value to
> the value of the number of rows in the table. Not only did my attempt to
> add
> a single new company to the companies table change all company names in
> that
> one industry to the new name, but I just discovered that it changed all
> rows
> in that column to the new company name:
>
>
At present the belief there is a bug in PostgreSQL is unsubstantiated.

I suggest you look internally for how an update command that caused the
resultant data could have been executed.  That is much more plausible, and
thus a better use of time, if you want to spend more time on this, than
trying to produce the observed behavior again using just insert and
setval(...) commands.

David J.


reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected]
  Subject: Re: Reset sequence to current maximum value of rows
  In-Reply-To: <CAKFQuwY-E_EuCHO+Q1o2Lc1d0r-TUp9f18UWRx1TtMEsLzDHvA@mail.gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox