From 5b7d305e8d122c3b5c815015256a132c4dbfc40d Mon Sep 17 00:00:00 2001 From: Etsuro Fujita Date: Wed, 18 Sep 2019 18:50:02 +0900 Subject: [PATCH] Doc: Update FDW documentation about direct foreign table modification. 1. Commit 7086be6e3 should have documented the limitation that the direct modification is disabled when WCO constraints are present, but didn't, which is definitely my fault. Update the documentation (Postgres 9.6 onwards). 2. Commit fc22b6623 should have documented the limitation that the direct modification is disabled when generated columns are defined, but didn't. Update the documentation (Postgres 12 onwards). Author: Etsuro Fujita Discussion: https://postgr.es/m/CAPmGK14AYCPunLb6TRz1CQsW5Le01Z2ox8LSOKH0P-cOVDcQRA%40mail.gmail.com --- doc/src/sgml/fdwhandler.sgml | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/doc/src/sgml/fdwhandler.sgml b/doc/src/sgml/fdwhandler.sgml index f719b06664..82cc282b9a 100644 --- a/doc/src/sgml/fdwhandler.sgml +++ b/doc/src/sgml/fdwhandler.sgml @@ -810,9 +810,11 @@ IsForeignRelUpdatable(Relation rel); row-by-row approach is necessary, but it can be inefficient. If it is possible for the foreign server to determine which rows should be modified without actually retrieving them, and if there are no local - triggers which would affect the operation, then it is possible to - arrange things so that the entire operation is performed on the remote - server. The interfaces described below make this possible. + structures which would affect the operation (row-level local triggers + or WITH CHECK OPTION constraints from parent views), + then it is possible to arrange things so that the entire operation is + performed on the remote server. The interfaces described below make + this possible.