Re: Mishandling of WCO constraints in direct foreign table modification

From: Etsuro Fujita <fujita(dot)etsuro(at)lab(dot)ntt(dot)co(dot)jp>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Mishandling of WCO constraints in direct foreign table modification
Date: 2017-07-21 03:00:03
Message-ID: 15aa9936-9bd8-c9e3-7ca1-3948610734b4@lab.ntt.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2017/07/21 3:24, Robert Haas wrote:
> I think that's reasonable. This should be committed and back-patched
> to 9.6, right?

Yeah, because direct modify was introduced in 9.6.

Attached is the second version which updated docs in postgres-fdw.sgml
as well.

Best regards,
Etsuro Fujita

Attachment Content-Type Size
fix-direct-modify-v2.patch text/plain 7.0 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Craig Ringer 2017-07-21 03:29:14 Re: [PATCH] pageinspect function to decode infomasks
Previous Message Amit Langote 2017-07-21 02:35:56 Re: [GENERAL] huge RAM use in multi-command ALTER of table heirarchy