diff options
| author | Etsuro Fujita <efujita@postgresql.org> | 2019-06-13 17:59:15 +0900 |
|---|---|---|
| committer | Etsuro Fujita <efujita@postgresql.org> | 2019-06-13 17:59:15 +0900 |
| commit | eddb79705f652f91ea1984172e5561d0ee05f27a (patch) | |
| tree | a66088d2093760267dcdaf1f8989d1370976a201 /contrib/postgres_fdw/sql | |
| parent | 1804185c2dbff2339e0d328ca9fbba1d19ff63df (diff) | |
| download | postgresql-eddb79705f652f91ea1984172e5561d0ee05f27a.tar.gz postgresql-eddb79705f652f91ea1984172e5561d0ee05f27a.zip | |
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
Diffstat (limited to 'contrib/postgres_fdw/sql')
| -rw-r--r-- | contrib/postgres_fdw/sql/postgres_fdw.sql | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/contrib/postgres_fdw/sql/postgres_fdw.sql b/contrib/postgres_fdw/sql/postgres_fdw.sql index a439239bff6..1a4718d1c62 100644 --- a/contrib/postgres_fdw/sql/postgres_fdw.sql +++ b/contrib/postgres_fdw/sql/postgres_fdw.sql @@ -677,6 +677,11 @@ SELECT * from loc1; UPDATE rem1 set f2 = 'skidoo' RETURNING f2; SELECT * from loc1; +EXPLAIN (verbose, costs off) +UPDATE rem1 set f1 = 10; -- all columns should be transmitted +UPDATE rem1 set f1 = 10; +SELECT * from loc1; + DELETE FROM rem1; -- Add a second trigger, to check that the changes are propagated correctly |