Skip to content

Commit 879b69b

Browse files
author
Etsuro Fujita
committed
Doc: Update FDW documentation about direct foreign table modification.
1. Commit 7086be6 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 fc22b66 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
1 parent 8972ac6 commit 879b69b

File tree

1 file changed

+5
-3
lines changed

1 file changed

+5
-3
lines changed

doc/src/sgml/fdwhandler.sgml

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -724,9 +724,11 @@ IsForeignRelUpdatable (Relation rel);
724724
row-by-row approach is necessary, but it can be inefficient. If it is
725725
possible for the foreign server to determine which rows should be
726726
modified without actually retrieving them, and if there are no local
727-
triggers which would affect the operation, then it is possible to
728-
arrange things so that the entire operation is performed on the remote
729-
server. The interfaces described below make this possible.
727+
structures which would affect the operation (row-level local triggers
728+
or <literal>WITH CHECK OPTION</literal> constraints from parent views),
729+
then it is possible to arrange things so that the entire operation is
730+
performed on the remote server. The interfaces described below make
731+
this possible.
730732
</para>
731733

732734
<para>

0 commit comments

Comments
 (0)