Feedback-ID: i76984098:Fastmail
Message-ID: <c6ca9286-a0ea-48bb-adb0-2d4e1835ebee@aklaver.com>
Date: Tue, 11 Mar 2025 08:12:40 -0700
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: Duplicate Key Values
To: mark bradley <markbradyju@outlook.com>
Cc: pgsql-general <pgsql-general@postgresql.org>
References: <CH3PR22MB4312C23476C0E67F9B4C2E10BACB2@CH3PR22MB4312.namprd22.prod.outlook.com>
 <SJ2PR22MB4328C53DB4397EB9759419DDBACA2@SJ2PR22MB4328.namprd22.prod.outlook.com>
 <6aee94f9-d421-4622-bccc-bdac37969be0@aklaver.com>
 <SJ2PR22MB4328C88FCBA2B447CC72DC90BACA2@SJ2PR22MB4328.namprd22.prod.outlook.com>
 <b21040db-9b7f-414c-9d11-da08685e1a81@aklaver.com>
 <SJ2PR22MB4328931B7CB951A48F1434ABBACA2@SJ2PR22MB4328.namprd22.prod.outlook.com>
 <75b33741-ee99-4524-b63a-edad21c1266d@aklaver.com>
 <SJ2PR22MB43286857EAC74D1EE332B08CBAD52@SJ2PR22MB4328.namprd22.prod.outlook.com>
 <9d919848-3fe1-46fd-b343-c5f2931864f7@aklaver.com>
 <SJ2PR22MB43282F7C60DD81CA90502FA0BAD52@SJ2PR22MB4328.namprd22.prod.outlook.com>
 <513ddbee-135c-4af2-b6f6-acca667b8d09@aklaver.com>
 <SJ2PR22MB4328C3D2704FB8F6CD079924BAD12@SJ2PR22MB4328.namprd22.prod.outlook.com>
 <d9c4c12e-fcf9-44a6-becc-f7c852f62ed4@aklaver.com>
 <SJ2PR22MB4328267BD9F601D90601715BBAD12@SJ2PR22MB4328.namprd22.prod.outlook.com>
Content-Language: en-US
From: Adrian Klaver <adrian.klaver@aklaver.com>
In-Reply-To: <SJ2PR22MB4328267BD9F601D90601715BBAD12@SJ2PR22MB4328.namprd22.prod.outlook.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://www.postgresql.org/message-id/c6ca9286-a0ea-48bb-adb0-2d4e1835ebee%40aklaver.com>
Precedence: bulk

On 3/11/25 08:05, mark bradley wrote:
> The rows that were preserved in the nodes table were the ones that were 
> not dups originally.

1) To be specific:

a) If there where two or more rows with a node_id, after the reindexing 
was there only one left?

b) Or for any node_ids that where duplicated did reindexing eliminate 
all rows with that node_id.


2) Per post from Greg Sabino Mullane, you need to show us the steps you 
took to reindex the table.

> 
> 
> Best regards,
> Mark Brady
> _amazon.com/author/markjbrady <https://amazon.com/author/markjbrady>_
> ------------------------------------------------------------------------
> *From:* Adrian Klaver <adrian.klaver@aklaver.com>
> *Sent:* Tuesday, March 11, 2025 10:56 AM
> *To:* mark bradley <markbradyju@outlook.com>
> *Cc:* pgsql-general <pgsql-general@postgresql.org>
> *Subject:* Re: Duplicate Key Values
> On 3/11/25 07:28, mark bradley wrote:
>> An "interesting" effect of reindexing is that all the records that were 
>> dups in the nodes table were deleted, both copies.
> 
> I am trying to understand above.
> 
> Was there at least one row of each node_id left?
> 
>> 
>> Also, all rows having node_id as a foreign key in other tables were 
>> deleted, which means all rows in these tables were deleted.
>> 
>> Fortunately these are not huge tables.  I will reenter the data, make a 
>> backup, and then try your further extended suggestions.
>> 
>> Best regards,
>> Mark Brady
>> _amazon.com/author/markjbrady <https://amazon.com/author/markjbrady 
> <https://amazon.com/author/markjbrady>>_
> 
> 
> -- 
> Adrian Klaver
> adrian.klaver@aklaver.com
> 

-- 
Adrian Klaver
adrian.klaver@aklaver.com