Re: wCTE behaviour

From: Marko Tiikkaja <marko(dot)tiikkaja(at)cs(dot)helsinki(dot)fi>
To: David Fetter <david(at)fetter(dot)org>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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-01-15 20:23:43
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

On 2010-12-23 6:55 PM +0200, David Fetter wrote:
> Here's a document-included version :)

And here's the latest version of the patch for the last commit fest for 9.1.

I fixed an issue with the portal logic, and now we use
PORTAL_ONE_RETURNING for wCTE queries, even if the main query is not a
DML or does not have RETURNING. This also means that we materialize the
results of the main query sometimes unnecessarily, but that doesn't look
like an easy thing to fix. PORTAL_ONE_RETURNING as a name is also a bit
misleading now, so maybe that needs changing..

Any feedback welcome.

Marko Tiikkaja

Attachment Content-Type Size
wcte.patch text/plain 72.7 KB

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Marko Tiikkaja 2011-01-15 20:30:14 Re: Review: Fix snapshot taking inconsistencies
Previous Message Dimitri Fontaine 2011-01-15 20:16:25 Re: pg_basebackup for streaming base backups