Re: Parameterized-path cost comparisons need some work

Excerpts from Robert Haas's message of mar abr 17 15:46:23 -0300 2012:
> On Tue, Apr 17, 2012 at 12:14 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> > The core of the patch is in the new functions get_baserel_parampathinfo
> > and get_joinrel_parampathinfo, which look up or construct ParamPathInfos,
> > and join_clause_is_parameterizable_for and
> > join_clause_is_parameterizable_within, which control
> > movement of parameterizable join clauses.  (I'm not that thrilled with the
> > names of the latter two functions, anybody got a better idea?)  The rest
> > of it is pretty much boilerplate changes and replacing ad-hoc logic with
> > uses of this stuff.
>
> Parameterizable is such a mouthful. I wish we had a better word.

P13e ?

--
Álvaro Herrera <alvherre(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support