Re: efficient data reduction (and deduping) - Mailing list pgsql-performance

From Claudio Freire
Subject Re: efficient data reduction (and deduping)
Date
Msg-id CAGTBQpaBKj8e8wrBrF8+HjNyNKOrJrCBqdCyj1ZR+3ssXjK3sQ@mail.gmail.com
Whole thread Raw
In response to Re: efficient data reduction (and deduping)  (Alessandro Gagliardi <alessandro@path.com>)
Responses Re: efficient data reduction (and deduping)
Re: efficient data reduction (and deduping)
List pgsql-performance
On Thu, Mar 1, 2012 at 4:35 PM, Alessandro Gagliardi
<alessandro@path.com> wrote:
> Interesting solution. If I'm not mistaken, this does solve the problem of
> having two entries for the same user at the exact same time (which violates
> my pk constraint) but it does so by leaving both of them out (since there is
> no au1.hr_timestamp > au2.hr_timestamp in that case). Is that right?

Yes, but it would have to be same *exact* time (not same hour).

You can use more fields to desambiguate too, ie:

au1.hr_timestamp > au2.hr_timestamp or (au1.hr_timestamp ==
au2.hr_timestamp and au1.some_other_field > au2.some_other_field)

If you have a sequential id to use in desambiguation, it would be best.

pgsql-performance by date:

Previous
From: Alessandro Gagliardi
Date:
Subject: Re: efficient data reduction (and deduping)
Next
From: Claudio Freire
Date:
Subject: Re: efficient data reduction (and deduping)