Re: NULL-handling in aggregate(DISTINCT ...)

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: NULL-handling in aggregate(DISTINCT ...)
Date: 2009-11-12 14:53:26
Message-ID: 24100.1258037606@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk> writes:
> A followup question: currently the code uses the "datum" interface for
> tuplesort. Obviously with multiple columns the slot interface is used
> instead; but is there any performance advantage for staying with the
> datum interface for the single-column case?

No idea ... measure it and see.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Marko Kreen 2009-11-12 15:01:40 Re: recovery is stuck when children are not processing SIGQUIT from previous crash
Previous Message Tom Lane 2009-11-12 14:52:24 Re: write ahead logging in standby (streaming replication)