Etsuro Fujita 8b6da83d16 postgres_fdw: Account for triggers in non-direct remote UPDATE planning.
Previously, in postgresPlanForeignModify, we planned an UPDATE operation
on a foreign table so that we transmit only columns that were explicitly
targets of the UPDATE, so as to avoid unnecessary data transmission, but
if there were BEFORE ROW UPDATE triggers on the foreign table, those
triggers might change values for non-target columns, in which case we
would miss sending changed values for those columns.  Prevent optimizing
away transmitting all columns if there are BEFORE ROW UPDATE triggers on
the foreign table.

This is an oversight in commit 7cbe57c34 which added triggers on foreign
tables, so apply the patch all the way back to 9.4 where that came in.

Author: Shohei Mochizuki
Reviewed-by: Amit Langote
Discussion: https://postgr.es/m/201905270152.x4R1q3qi014550@toshiba.co.jp
2019-06-13 17:59:09 +09:00
..
2019-01-02 12:44:25 -05:00
2019-05-22 13:04:48 -04:00
2019-01-02 12:44:25 -05:00
2019-05-22 13:04:48 -04:00
2019-05-22 13:04:48 -04:00
2019-06-03 13:44:03 +09:00
2019-05-22 12:55:34 -04:00
2019-05-22 13:04:48 -04:00
2019-01-02 12:44:25 -05:00
2019-01-02 12:44:25 -05:00
2019-05-22 13:04:48 -04:00
2019-01-02 12:44:25 -05:00
2019-05-22 13:04:48 -04:00
2019-01-02 12:44:25 -05:00
2017-09-14 22:22:59 -04:00
2019-05-22 13:04:48 -04:00
2019-05-22 13:04:48 -04:00
2019-01-02 12:44:25 -05:00
2019-05-22 13:04:48 -04:00
2019-05-22 13:04:48 -04:00
2017-06-21 15:35:54 -04:00
2019-05-22 13:04:48 -04:00
2019-01-02 12:44:25 -05:00
2019-01-02 12:44:25 -05:00
2019-05-22 13:04:48 -04:00
2018-04-03 09:47:18 -04:00

The PostgreSQL contrib tree
---------------------------

This subtree contains porting tools, analysis utilities, and plug-in
features that are not part of the core PostgreSQL system, mainly
because they address a limited audience or are too experimental to be
part of the main source tree.  This does not preclude their
usefulness.

User documentation for each module appears in the main SGML
documentation.

When building from the source distribution, these modules are not
built automatically, unless you build the "world" target.  You can
also build and install them all by running "make all" and "make
install" in this directory; or to build and install just one selected
module, do the same in that module's subdirectory.

Some directories supply new user-defined functions, operators, or
types.  To make use of one of these modules, after you have installed
the code you need to register the new SQL objects in the database
system by executing a CREATE EXTENSION command.  In a fresh database,
you can simply do

    CREATE EXTENSION module_name;

See the PostgreSQL documentation for more information about this
procedure.