pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Etsuro Fujita <fujita.etsuro@lab.ntt.co.jp>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Ashutosh Bapat <ashutosh.bapat@enterprisedb.com>
Cc: Ildus Kurbangaliev <i.kurbangaliev@postgrespro.ru>
Cc: Dilip Kumar <dilipbalaut@gmail.com>
Cc: PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Cc: Robert Haas <robertmhaas@gmail.com>
Subject: Re: [HACKERS] Bug in ExecModifyTable function and trigger issues for foreign tables
Date: Mon, 27 Nov 2017 14:38:12 +0900
Message-ID: <5A1BA4C4.3060508@lab.ntt.co.jp> (raw)
In-Reply-To: <14028.1511736992@sss.pgh.pa.us>
References: <20170514150525.0346ba72@postgrespro.ru>
	<CAFjFpRcQudmKYU4PJRN1-wp5K4aksupSoVpcRVAzES_49T=Vng@mail.gmail.com>
	<20170516150516.1b616230@wp.localdomain>
	<CAFjFpReeA3G3-U-FsR79zx_xFBVZc73hhWcH4OVWMb+ZFViRQg@mail.gmail.com>
	<dbf4b9ff-b0be-2396-7c79-d5763ae8a034@lab.ntt.co.jp>
	<f62d1797-2817-0f2e-eb7b-38da40504c8d@lab.ntt.co.jp>
	<a31f779e-9cb8-1ea5-71a6-bca6adbfa6a4@lab.ntt.co.jp>
	<20170615180548.5e142ddc@wp.localdomain>
	<0bc9c28b-96ca-c875-871e-16af6f53ecd9@lab.ntt.co.jp>
	<CAFjFpReUW9JhuyEq5mhi2Hrt3KpjHHP8LnWBZQhrHek3c0KGVQ@mail.gmail.com>
	<428f1672-df54-de01-91da-b57365193bf4@lab.ntt.co.jp>
	<d0a12e42-e20a-b561-76ed-7fa48d4b520a@lab.ntt.co.jp>
	<6c651916-8fde-f9c9-b199-080df1bf2867@lab.ntt.co.jp>
	<280720c5-7aad-1136-6be3-654208c8f714@lab.ntt.co.jp>
	<8065.1500475011@sss.pgh.pa.us>
	<9cd25d80-08fc-568c-3181-dbe98723d0db@lab.ntt.co.jp>
	<3e9ff40d-d00f-3363-dcee-97ce023c7884@lab.ntt.co.jp>
	<f8aa99d0-627d-32dc-fbc7-4e5943f9d652@lab.nt! t.co.jp>
	<14028.1511736992@sss.pgh.pa.us >

(2017/11/27 7:56), Tom Lane wrote:
> Etsuro Fujita<fujita.etsuro@lab.ntt.co.jp>  writes:
>> [ fix-rewrite-tlist-v4.patch ]
>
> I started reviewing this patch.

Great!

> I did not much like the fact that it
> effectively moved rewriteTargetListUD to a different file and renamed it.
> That seems like unnecessary code churn, plus it breaks the analogy with
> rewriteTargetListIU, plus it will make back-patching harder (since that
> code isn't exactly the same in back branches).  I see little reason why
> we can't leave it where it is and just make it non-static.  It's not like
> there's no other parts of the rewriter that the planner calls.

Agreed.

Best regards,
Etsuro Fujita




view thread (43+ messages)  latest in thread

Message-ID: <5A1BA4C4.3060508@lab.ntt.co.jp>
Permalink:  ../5A1BA4C4.3060508@lab.ntt.co.jp/
Also on:    postgresql.org/message-id/5A1BA4C4.3060508@lab.ntt.co.jp

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: fujita.etsuro@lab.ntt.co.jp, tgl@sss.pgh.pa.us, ashutosh.bapat@enterprisedb.com, i.kurbangaliev@postgrespro.ru, dilipbalaut@gmail.com, robertmhaas@gmail.com
  Subject: Re: [HACKERS] Bug in ExecModifyTable function and trigger issues for foreign tables
  In-Reply-To: <5A1BA4C4.3060508@lab.ntt.co.jp>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox