Re: optimizing constant quals within outer joins - Mailing list pgsql-hackers

From Tom Lane
Subject Re: optimizing constant quals within outer joins
Date
Msg-id 18508.1151794519@sss.pgh.pa.us
Whole thread Raw
In response to Re: optimizing constant quals within outer joins  (Alvaro Herrera <alvherre@commandprompt.com>)
Responses Re: optimizing constant quals within outer joins  (Alvaro Herrera <alvherre@commandprompt.com>)
List pgsql-hackers
Alvaro Herrera <alvherre@commandprompt.com> writes:
> I note that the rowcount is not altered by the one-time filter.  Is this
> an issue?  I imagine the problem is not being able to estimate the
> number of rows that pass the filter.

That's intentional.  The filter is either going to pass all or none of
the rows, not some fraction of them.  It clearly isn't very reasonable
to guess that it will pass none of them (except if the qual is actually
constant FALSE).

> I also wonder whether it wouldn't be better in this case to apply each
> filter to each arm of the merge join.

Uh, why?  For the most part, I'd think the higher you can put the filter
in the plan tree, the better.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: optimizing constant quals within outer joins
Next
From: Alvaro Herrera
Date:
Subject: Re: optimizing constant quals within outer joins