Horton

Re: [HACKERS] Another oddity in handling of WCO constraints in postgres_fdw

Jeff Davis <pgsql@j-davis.com>

View thread View on postgr.es
From: Jeff Davis <pgsql@j-davis.com>
To: Etsuro Fujita <fujita.etsuro@lab.ntt.co.jp>, Arthur Zakirov <a.zakirov@postgrespro.ru>
Cc: Stephen Frost <sfrost@snowman.net>, Robert Haas <robertmhaas@gmail.com>, Ashutosh Bapat <ashutosh.bapat@enterprisedb.com>, pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2018-07-09T00:00:18Z
Lists: pgsql-hackers 
On Tue, 2018-03-06 at 20:09 +0900, Etsuro Fujita wrote:
> Agreed.  I added a comment to that function.  I think that that
> comment 
> in combination with changes to the FDW docs in the patch would help
> FDW 
> authors understand why that is needed.  Please find attached an
> updated 
> version of the patch.
> 
> Thanks for the comments!

Committed.

I made some small modifications and added a test for the case where the
foreign table is a partition of a local table, which follows a
different code path after commit 3d956d95.

Thank you!

Regards,
	Jeff Davis

Commits

  1. Fix WITH CHECK OPTION on views referencing postgres_fdw tables.

  2. Allow insert and update tuple routing and COPY for foreign tables.

  3. When WCOs are present, disable direct foreign table modification.