| From: | Marko Tiikkaja <marko(dot)tiikkaja(at)cs(dot)helsinki(dot)fi> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Hitoshi Harada <umi(dot)tanuki(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: How to share the result data of separated plan |
| Date: | 2010-11-07 16:35:48 |
| Message-ID: | 4CD6D564.1050500@cs.helsinki.fi |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2010-11-07 6:23 PM +0200, Tom Lane wrote:
> Hitoshi Harada<umi(dot)tanuki(at)gmail(dot)com> writes:
>> Up to now, in a portal we only have multiple plans that share nothing
>> but relations, then executor starts, runs and ends separately.
>> Writeable CTEs need the result tuplestore of separated plans that were
>> executed before main query .
>
> Um ... why? I thought the whole point of breaking out ModifyTable
> as a separate node type was so that a query involving writeable CTEs
> would still be just one plan tree.
We tried that for 9.0 and it didn't work. Almost all work for 9.1 has
been spent on creating an infrastructure for running the executor
separately for every WITH list element when wCTEs are present.
Regards,
Marko Tiikkaja
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gurjeet Singh | 2010-11-07 17:39:08 | Re: Patch to add a primary key using an existing index |
| Previous Message | Tom Lane | 2010-11-07 16:23:46 | Re: How to share the result data of separated plan |