public inbox for [email protected]
help / color / mirror / Atom feedFrom: mark bradley <[email protected]>
To: Adrian Klaver <[email protected]>
To: Ron Johnson <[email protected]>
To: pgsql-general <[email protected]>
Subject: Re: Duplicate Key Values
Date: Thu, 6 Mar 2025 18:14:14 +0000
Message-ID: <SJ2PR22MB432898722A74E9B808AC4F05BACA2@SJ2PR22MB4328.namprd22.prod.outlook.com> (raw)
In-Reply-To: <SJ2PR22MB4328C53DB4397EB9759419DDBACA2@SJ2PR22MB4328.namprd22.prod.outlook.com>
References: <CH3PR22MB4312C23476C0E67F9B4C2E10BACB2@CH3PR22MB4312.namprd22.prod.outlook.com>
<CANzqJaDWzZ4O10QZi6w__N5q7gzwcZANfu0DxA7UOpFwqAqTyQ@mail.gmail.com>
<SJ2PR22MB43284AE4E32208EB035F68F5BACB2@SJ2PR22MB4328.namprd22.prod.outlook.com>
<CANzqJaCZefaoZqJzPSFqEaRA1W-Ps5E6yNuL_PT-WxUw9x38Nw@mail.gmail.com>
<[email protected]>
<SJ2PR22MB4328C53DB4397EB9759419DDBACA2@SJ2PR22MB4328.namprd22.prod.outlook.com>
I tried adding a dummy column with different values and then deleting one, as you suggested. Got the same message.
Mark Brady, Ph.D.
Deputy Chief Data Officer, TRMC
amazon.com/author/markjbrady<https://amazon.com/author/markjbrady;
________________________________
From: mark bradley <[email protected]>
Sent: Thursday, March 6, 2025 1:11 PM
To: Adrian Klaver <[email protected]>; Ron Johnson <[email protected]>; pgsql-general <[email protected]>
Subject: Re: Duplicate Key Values
Here is the table definition:
[cid:ecac8e92-826b-45c8-95a8-aaf0e55c4f9c]
And here is the error message I get when I try to delete a duplicate:
[cid:a0f5f298-984d-4f89-abd2-475c02e65b9d]
Mark Brady,
amazon.com/author/markjbrady<https://amazon.com/author/markjbrady;
________________________________
From: Adrian Klaver <[email protected]>
Sent: Wednesday, March 5, 2025 6:49 PM
To: Ron Johnson <[email protected]>; pgsql-general <[email protected]>
Subject: Re: Duplicate Key Values
On 3/5/25 15:37, Ron Johnson wrote:
> What does "and unique identifier" mean?
>
> (Creating a Primary Key constraint automatically creates a unique
> no-nulls-allowed index on the column(s), so no other index is needed.)
>
> Can you show the table definition?
>
> Anyway, you /should/ be able to delete one of the duplicate node_id
> records by specifying another column with a different value;
>
> On Wed, Mar 5, 2025 at 6:14 PM mark bradley <[email protected]
> <mailto:[email protected]>> wrote:
>
> Hi Ron,
>
> The key is an integer. I'm using pGAdmin4 and recently updated to
> the latest version.
1) Did you not see duplicates with the old version of pgAdmin4?
2) What do you see if you use psql?
3) Did you upgrade/move the Postgres server or the underlying OS?
4) Have you tried reindexing the node_id field?
>
> The records are not all identical, some have NULL values of the
> non-key for some unknown reason. Here is a screenshot. The key is
> node_id, which I have specified as a key and unique identifier.
>
>
>
--
Adrian Klaver
[email protected]
Attachments:
[image/png] image.png (30.4K, 3-image.png)
download | view image
[image/png] image.png (23.4K, 4-image.png)
download | view image
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: Duplicate Key Values
In-Reply-To: <SJ2PR22MB432898722A74E9B808AC4F05BACA2@SJ2PR22MB4328.namprd22.prod.outlook.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