From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | pgsql-hackers(at)postgreSQL(dot)org |
Subject: | Status of DISTINCT-by-hashing work |
Date: | 2008-08-05 14:51:25 |
Message-ID: | 5567.1217947885@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
I've pretty much finished the project I got a bee in my bonnet about
last week, which is to teach SELECT DISTINCT how to (optionally) use
hashing for grouping in the same way that GROUP BY has been able to do
for awhile.
There are still two places in the system that hard-wire the use of
sorting for duplicate elimination:
* Set operations (UNION/INTERSECT/EXCEPT)
* Aggregate functions with DISTINCT
I'm thinking of trying to fix set operations before I leave this topic,
but I'm not sure it's worth the trouble to change DISTINCT aggregates.
They'd be a lot more work (since there's no executor infrastructure
in place that could be used) and the return on investment seems low.
Comments?
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Magnus Hagander | 2008-08-05 14:53:56 | Re: BUG #4186: set lc_messages does not work |
Previous Message | Magnus Hagander | 2008-08-05 14:44:14 | Re: Parsing of pg_hba.conf and authentication inconsistencies |