From: Richard Huxton <dev@archonet.com>
To: Christophe <xof@thebuild.com>
Cc: pgsql-sql@postgresql.org
Subject: Re: De-duplicating rows
Date: Fri, 17 Jul 2009 08:21:01 +0100
Message-ID: <4A60265D.1060905@archonet.com> (raw)
In-Reply-To: <87E8E647-4CAD-4491-B687-FA763E0EBE7E@thebuild.com>
References: <87E8E647-4CAD-4491-B687-FA763E0EBE7E@thebuild.com>
Christophe wrote:
> The Subject: is somewhat imprecise, but here's what I'm trying to do.
> For some reason, my brain is locking up over it.
>
> I'm moving a 7.2 (yes) database to 8.4. >
Big leap. Allow some time for testing your application. I'm not sure if
7.2 even supported schemas, and there's been loads of tightening up the
rules for automatic type casting, unicode etc.
> Now, since this database has been production since 7.2 days, cruft has
> crept in: in particular, there are duplicate email addresses, some with
> mismatched attributes. The policy decision by the client is that the
> correct row is the one with the earliest timestamp.
Something like (untested):
CREATE TEMPORARY TABLE earliest_duplicates AS
SELECT
email AS tgt_email,
min(create_date) AS tgt_date
FROM mytable
GROUP BY email
HAVING count(*) > 1;
DELETE FROM mytable USING earliest duplicates
WHERE email=tgt_email AND create_date > tgt_date;
--
Richard Huxton
Archonet Ltd
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: pgsql-sql@postgresql.org
Cc: dev@archonet.com, xof@thebuild.com
Subject: Re: De-duplicating rows
In-Reply-To: <4A60265D.1060905@archonet.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox