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: | Robert Haas <robertmhaas(at)gmail(dot)com>, 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-08 17:03:10 |
Message-ID: | 4CD82D4E.8060107@cs.helsinki.fi |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 2010-11-08 6:38 PM +0200, Tom Lane wrote:
> Robert Haas<robertmhaas(at)gmail(dot)com> writes:
>> On Sun, Nov 7, 2010 at 1:08 PM, Tom Lane<tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>>> I guess I shoulda been paying closer attention :-(. That really, really
>>> seems like fundamentally the wrong direction. What was it that was
>>> unfixable about the other way? If it is unfixable, should we revert
>>> ModifyTable?
>
>> The relevant thread is here:
>> http://archives.postgresql.org/pgsql-hackers/2010-02/msg00783.php
>
> My opinion is still the same as here:
> http://archives.postgresql.org/pgsql-hackers/2010-02/msg00688.php
>
> namely, that all we should be worrying about is a tuplestore full of
> RETURNING tuples. Any other side-effects of a DML subquery should
> *not* be visible to the calling query, and therefore all this argument
> about snapshots and seqscan limits is beside the point.
What happened to:
http://archives.postgresql.org/pgsql-hackers/2009-10/msg00566.php ?
Regards,
Marko Tiikkaja
From | Date | Subject | |
---|---|---|---|
Next Message | Hitoshi Harada | 2010-11-08 17:16:33 | Re: How to share the result data of separated plan |
Previous Message | Tom Lane | 2010-11-08 17:00:42 | Re: Protecting against unexpected zero-pages: proposal |