Re: COPY (INSERT/UPDATE/DELETE .. RETURNING ..) - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: COPY (INSERT/UPDATE/DELETE .. RETURNING ..)
Date
Msg-id CAB7nPqSAfK4YH7_fx5aYo=UyHcSeWkfAYamz8SCGAH_X-CbYvQ@mail.gmail.com
Whole thread Raw
In response to Re: COPY (INSERT/UPDATE/DELETE .. RETURNING ..)  (Marko Tiikkaja <marko@joh.to>)
Responses Re: COPY (INSERT/UPDATE/DELETE .. RETURNING ..)  (Marko Tiikkaja <marko@joh.to>)
List pgsql-hackers
On Thu, Nov 19, 2015 at 11:04 AM, Marko Tiikkaja wrote:
> This was discussed in 2010 when CTEs got the same treatment, and I agree
> with what was decided back then.  If someone needs to make PreparableStmt
> different from what COPY and CTEs support, we can split them up.  But
> they're completely identical after this patch, so splitting them up right
> now is somewhat pointless.
> Further, if someone's going to add new stuff to PreparableStmt, she should
> probably think about whether it would make sense to add it to COPY and CTEs
> from day one, too, and in that case not splitting them up is actually a win.

Personally, I would take it on the safe side and actually update it.
If someone were to add a new node type in PreparableStmt I am pretty
sure that we are going to forget to update the COPY part, leading us
to unwelcome bugs. And that would not be cool.
-- 
Michael



pgsql-hackers by date:

Previous
From: Kouhei Kaigai
Date:
Subject: Re: Foreign join pushdown vs EvalPlanQual
Next
From: Thom Brown
Date:
Subject: Re: Error with index on unlogged table