| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Vaibhav Kaushal <vaibhavkaushal123(at)gmail(dot)com> |
| Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Where the Quals are actually 'List'ed |
| Date: | 2011-02-07 16:16:42 |
| Message-ID: | 16762.1297095402@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Vaibhav Kaushal <vaibhavkaushal123(at)gmail(dot)com> writes:
> Hi,
> I find that ExecInitExpr creates a ExprState tree (and so say the
> comments above the function in the source). Also, it seems to decide
> which function would get called when the expression is to be evaluated
> when ExecQual runs, by setting the function pointer, for example:
> bstate->xprstate.evalfunc = (ExprStateEvalFunc)ExecEvalAnd;
> But ExecQual goes through a List, whereas, ExecInitExpr creates a tree.
> So is that same tree converted to a qual list or are we adding some more
> information.
ExecInitExpr produces a List of state trees from a List of expr trees
--- look at the last case in its switch.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dimitri Fontaine | 2011-02-07 16:23:08 | Re: A different approach to extension NO USER DATA feature |
| Previous Message | Tom Lane | 2011-02-07 16:12:07 | Re: Varlena and binary |