From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Marko Tiikkaja <marko(dot)tiikkaja(at)cs(dot)helsinki(dot)fi> |
Cc: | David Fetter <david(at)fetter(dot)org>, Peter Eisentraut <peter_e(at)gmx(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Robert Haas <robertmhaas(at)gmail(dot)com>, Yeb Havinga <yebhavinga(at)gmail(dot)com>, Hitoshi Harada <umi(dot)tanuki(at)gmail(dot)com> |
Subject: | Re: wCTE behaviour |
Date: | 2011-02-25 17:17:55 |
Message-ID: | 26007.1298654275@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Marko Tiikkaja <marko(dot)tiikkaja(at)cs(dot)helsinki(dot)fi> writes:
> On 2011-02-25 6:12 PM, Tom Lane wrote:
>> The current implementation with everything in one plantree
>> really ought to look just like a SELECT so far as the portal code
>> is concerned.
> The problem was that the old code was using PORTAL_MULTI_QUERY whenever
> a wCTE was present. Are you saying that you are using
> PORTAL_ONE_SELECT? Doesn't that have problems with triggers, for example?
Hmmm ... good question. I notice the lack of any regression test cases
involving triggers. Will check this.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Greg Stark | 2011-02-25 17:31:05 | Re: wCTE: why not finish sub-updates at the end, not the beginning? |
Previous Message | Rod Taylor | 2011-02-25 17:03:58 | Re: WIP: cross column correlation ... |