Re: [HACKERS] Account for cost and selectivity of HAVING quals - Mailing list pgsql-hackers

From David G. Johnston
Subject Re: [HACKERS] Account for cost and selectivity of HAVING quals
Date
Msg-id CAKFQuwb=ZKj1RnJBt4fn1xhBdRJGPJfsHEs0HYrNgD9zgvU35g@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] Account for cost and selectivity of HAVING quals  ("Tels" <nospam-pg-abuse@bloodgate.com>)
Responses Re: [HACKERS] Account for cost and selectivity of HAVING quals  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: [HACKERS] Account for cost and selectivity of HAVING quals  ("Tels" <nospam-pg-abuse@bloodgate.com>)
List pgsql-hackers
On Tue, Oct 31, 2017 at 4:31 PM, Tels <nospam-pg-abuse@bloodgate.com> wrote:

​​
That looks odd to me, it first uses output_tuples in a formula, then
overwrites the value with a new value. Should these lines be swapped?

​IIUC it is correct: the additional total_cost comes from processing every output group to check whether it is qualified - since every group is checked the incoming output_tuples from the prior grouping is used.  The side-effect of the effort is that the number of output_tuples has now been reduced to only those matching the qual - and so it now must take on a new value to represent this.

David J.​

pgsql-hackers by date:

Previous
From: Oleg Ivanov
Date:
Subject: [HACKERS] Proposal: generic WAL compression
Next
From: Tom Lane
Date:
Subject: Re: [HACKERS] Account for cost and selectivity of HAVING quals