|From:||Bruce Momjian <bruce(at)momjian(dot)us>|
|To:||Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>|
|Cc:||Merlin Moncure <mmoncure(at)gmail(dot)com>, Daniel Browning <db(at)kavod(dot)com>, pgsql-hackers(at)postgresql(dot)org|
|Subject:||Re: CTE optimization fence on the todo list?|
|Views:||Raw Message | Whole Thread | Download mbox | Resend email|
On Mon, Oct 1, 2012 at 10:07:01AM -0400, Tom Lane wrote:
> Merlin Moncure <mmoncure(at)gmail(dot)com> writes:
> > I'm wondering if there are any technical/standards constraints that
> > are behind the fencing behavior.
> I think the key reason is that we don't want partial execution of DML
> operations (ie, INSERT/UPDATE/DELETE inside a WITH). The fencing
> behavior was put in originally because we foresaw adding DML later.
> We could possibly relax the rule for WITH SELECT only, but it would
> be rather inconsistent, not to mention unpleasant for all the people
> who are relying on the current behavior for one reason or another.
> Another issue is that if the CTE is scanned multiple times by the outer
> query, you really can't optimize it on the basis of any one call site.
If we wanted to relax the fencing, we might need to do it via an SQL
keyword on the SELECT, to avoid the confusion caused by GUCs.
+ It's impossible for everything to be true. +
|Next Message||Tom Lane||2012-10-01 15:00:35||Re: pg_malloc() versus malloc(0)|
|Previous Message||Tom Lane||2012-10-01 14:45:38||Re: pg_malloc() versus malloc(0)|