From: | Peter Geoghegan <pg(at)heroku(dot)com> |
---|---|
To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
Cc: | Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: PATCH: Extending the HyperLogLog API a bit |
Date: | 2016-01-19 21:54:07 |
Message-ID: | CAM3SWZT-i6R9JU5YXa8MJUou2_r3LfGJZpQ9tYa1BYxfkj0=cQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Jan 19, 2016 at 9:37 AM, Alvaro Herrera
<alvherre(at)2ndquadrant(dot)com> wrote:
> Our transcript seems to predate that bugfix commit, so I assume we need
> to apply this to our copy too. Sadly, Hideaki-san commit message isn't
> very descriptive.
Fortunately, the function mergeHyperLogLog() in our hyperloglog.c
currently has no callers.
> I don't really know how HyperLogLog works, so maybe we can't or
> shouldn't apply the patch because of how the hash stuff is used.
I think that Hideaki's confusion comes from whether or not this HLL
state is a sparse or dense/full representation. The distinction is
explained in the README for postgresql-hll:
https://github.com/aggregateknowledge/postgresql-hll
postgresql-hll has no support for merging HLLs that are sparse:
https://github.com/aggregateknowledge/postgresql-hll/blob/master/hll.c#L1888
Can't we just tear mergeHyperLogLog() out?
--
Peter Geoghegan
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2016-01-19 21:54:26 | Re: Combining Aggregates |
Previous Message | David Rowley | 2016-01-19 21:50:20 | Re: Combining Aggregates |