Re: BEFORE UPDATE trigger on postgres_fdw table not work

From: Etsuro Fujita <etsuro(dot)fujita(at)gmail(dot)com>
To: Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Shohei Mochizuki <shohei(dot)mochizuki(at)toshiba(dot)co(dot)jp>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: BEFORE UPDATE trigger on postgres_fdw table not work
Date: 2019-06-12 06:13:56
Message-ID: CAPmGK16LDH_mJ-VQ78655M2HaHpERibb1tRNWTNakALG-dNNSA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Jun 10, 2019 at 9:04 PM Etsuro Fujita <etsuro(dot)fujita(at)gmail(dot)com> wrote:
> I'll look into the patch more closely tomorrow.

I did that, but couldn't find any issue about the patch. Here is an
updated version of the patch. Changes are:

* Reworded the comments a bit in postgresPlanFoereignModify the
original patch modified
* Added the commit message

Does that make sense? I think this is an oversight in commit
7cbe57c34, so I'll back-patch all the way back to 9.4, if there are no
objections.

Best regards,
Etsuro Fujita

Attachment Content-Type Size
fix_fdw_update_trigger-efujita.patch application/octet-stream 5.6 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Timur Birsh 2019-06-12 06:20:44 [PATCH] vacuumlo: print the number of large objects going to be removed
Previous Message Amit Langote 2019-06-12 05:48:45 Re: Should we warn against using too many partitions?