|
I tried adding a dummy column with different values and then deleting one, as you suggested. Got the same message.
From: mark bradley <markbradyju@xxxxxxxxxxx>
Sent: Thursday, March 6, 2025 1:11 PM To: Adrian Klaver <adrian.klaver@xxxxxxxxxxx>; Ron Johnson <ronljohnsonjr@xxxxxxxxx>; pgsql-general <pgsql-general@xxxxxxxxxxxxxx> Subject: Re: Duplicate Key Values
Here is the table definition:
And here is the error message I get when I try to delete a duplicate:
Mark Brady,
From: Adrian Klaver <adrian.klaver@xxxxxxxxxxx>
Sent: Wednesday, March 5, 2025 6:49 PM To: Ron Johnson <ronljohnsonjr@xxxxxxxxx>; pgsql-general <pgsql-general@xxxxxxxxxxxxxx> 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 <markbradyju@xxxxxxxxxxx > <mailto:markbradyju@xxxxxxxxxxx>> 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 adrian.klaver@xxxxxxxxxxx |
