| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>, David Fetter <david(at)fetter(dot)org>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: LATERAL |
| Date: | 2009-12-20 04:01:35 |
| Message-ID: | 603c8f070912192001ndb259f5nd269e2476bc5453@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sat, Dec 19, 2009 at 4:46 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
>> On Sat, Dec 19, 2009 at 3:01 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>>> I believe the correct approach is probably to treat values that need to
>>> be propagated into the inner side as executor parameters. This could
>>> replace the existing, rather crocky, management of values passed into a
>>> nestloop inner indexscan.
>
>> What is the best place to look for the existing, rather crocky code?
>
> Follow the second argument of ExecReScan from nodeNestloop to
> nodeIndexscan.
Yeah, this is grotty. It appears that the comment introducing
ExecReScan() is somewhat incorrect. It asserts that exprCtxt is used
only
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2009-12-20 04:06:36 | Re: LATERAL |
| Previous Message | Bruce Momjian | 2009-12-20 03:59:13 | Re: Removing pg_migrator limitations |