Re: possible optimizations - pushing filter before aggregation

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Douglas Doole <dougdoole(at)gmail(dot)com>
Cc: Mithun Cy <mithun(dot)cy(at)enterprisedb(dot)com>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: possible optimizations - pushing filter before aggregation
Date: 2016-11-19 19:50:23
Message-ID: 19917.1479585023@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Douglas Doole <dougdoole(at)gmail(dot)com> writes:
> For min, you should be able to pre-filter =, < , and <=. In all cases the
> pre-filter would be <=. For max it would be =, > , >= becoming >=.

Doesn't really seem worth the trouble to me, given that those are pretty
unselective filter conditions. If you could push down an = then it might
be worth doing ...

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2016-11-19 19:54:12 Re: macaddr 64 bit (EUI-64) datatype support
Previous Message Stephen Frost 2016-11-19 19:29:42 Re: macaddr 64 bit (EUI-64) datatype support