Feedback-ID: i76984098:Fastmail
Message-ID: <28d34da0-c58c-4237-b71d-5907517ace45@aklaver.com>
Date: Tue, 10 Sep 2024 08:45:21 -0700
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: Removing duplicate rows in table
To: Rich Shepard <rshepard@appl-ecosys.com>, pgsql-general@postgresql.org
References: <e4688faf-de51-93ef-2db-f2acacbd658@appl-ecosys.com>
 <32765388-836c-4c00-bad0-665f0aa77ea8@aklaver.com>
 <19803246-8b24-5055-ef26-adf7ade3eb@appl-ecosys.com>
Content-Language: en-US
From: Adrian Klaver <adrian.klaver@aklaver.com>
In-Reply-To: <19803246-8b24-5055-ef26-adf7ade3eb@appl-ecosys.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://www.postgresql.org/message-id/28d34da0-c58c-4237-b71d-5907517ace45%40aklaver.com>
Precedence: bulk

On 9/10/24 08:29, Rich Shepard wrote:
> On Tue, 10 Sep 2024, Adrian Klaver wrote:
> 
>> Is there a Primary Key or Unique index on this table?
> 
> Adrian,
> 
> No. It didn't occur to me to make the project number a PK as this table is
> not related to others in the database.
> 
> But, yesterday it occurred to me to make the proj_nbr a PK to eliminate
> future issues.
> 

You might want to do something like:

select proj_nbr, count(*) as ct from projects group by proj_nbr;

to see how big a problem it is. If it is only a few projects it could 
just a matter of manually deleting the extras.

Whatever you do:

1) Make sure you have a backup of at least that table.

2) Do the data changes as BEGIN; <changes> COMMIT; or ROLLBACK;

> Thanks,
> 
> Rich
> 
> 

-- 
Adrian Klaver
adrian.klaver@aklaver.com