Re: COPY (INSERT/UPDATE/DELETE .. RETURNING ..)

From: Marko Tiikkaja <marko(at)joh(dot)to>
To: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
Cc: Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: COPY (INSERT/UPDATE/DELETE .. RETURNING ..)
Date: 2015-11-20 09:04:00
Message-ID: 564EE200.9070103@joh.to
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 11/19/15 7:39 PM, Michael Paquier wrote:
> On Thu, Nov 19, 2015 at 9:22 PM, Marko Tiikkaja <marko(at)joh(dot)to> wrote:
>> Of course, something might break if we added a new statement type which
>> supported RETURNING, but I'm really not worried about that. I'm not dead
>> set against adding some Assert(IsA()) calls here, but I don't see the point.
>
> gram.y has a long comment before select_no_parens regarding why we
> shouldn't do it this way, did you notice it?

It talks about not doing '(' SelectStmt ')' "in the expression
grammar". I don't see what that has to do with this patch.

.m

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Langote 2015-11-20 09:18:24 Re: Declarative partitioning
Previous Message Noah Misch 2015-11-20 08:11:36 Re: RLS open items are vague and unactionable