b REINDEX TABLE node;
Also reindexed table with node_id as a foreign key in the same way. Best regards, Mark Brady amazon.com/author/markjbrady<https://amazon.com/author/markjbrady> ________________________________ From: Adrian Klaver <[email protected]> Sent: Tuesday, March 11, 2025 11:12 AM To: mark bradley <[email protected]> Cc: pgsql-general <[email protected]> Subject: Re: Duplicate Key Values 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 <[email protected]> > *Sent:* Tuesday, March 11, 2025 10:56 AM > *To:* mark bradley <[email protected]> > *Cc:* pgsql-general <[email protected]> > *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 > [email protected] > -- Adrian Klaver [email protected]
