"Tom Lane" <[EMAIL PROTECTED]> writes: > This is important for making the world safe for hashed DISTINCT, since > AFAICS we probably can't ever use hashing for DISTINCT ON --- its definition > is too dependent on the assumption of sorting.
I don't think that's true. We could store the sort key in the hash along with the resulting tuple and replace the resulting tuple iff the new sort key is less than the old sort key. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's Slony Replication support! -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
