diff options
author | Peter Eisentraut <peter@eisentraut.org> | 2020-02-17 15:19:58 +0100 |
---|---|---|
committer | Peter Eisentraut <peter@eisentraut.org> | 2020-02-17 15:20:57 +0100 |
commit | ad3ae64770e5b4391ad07fb2a689d72aa45b4689 (patch) | |
tree | 3f4f1e3b334fc011903ff4281d15c7cd64b29086 /src/backend/utils/adt/jsonpath_exec.c | |
parent | f4ae7221413d5176e4d5a49883217ea87312104a (diff) | |
download | postgresql-ad3ae64770e5b4391ad07fb2a689d72aa45b4689.tar.gz postgresql-ad3ae64770e5b4391ad07fb2a689d72aa45b4689.zip |
Fill in extraUpdatedCols in logical replication
The extraUpdatedCols field of the target RTE records which generated
columns are affected by an update. This is used in a variety of
places, including per-column triggers and foreign data wrappers. When
an update was initiated by a logical replication subscription, this
field was not filled in, so such an update would not affect generated
columns in a way that is consistent with normal updates. To fix,
factor out some code from analyze.c to fill in extraUpdatedCols in the
logical replication worker as well.
Reviewed-by: Pavel Stehule <pavel.stehule@gmail.com>
Discussion: https://www.postgresql.org/message-id/flat/b05e781a-fa16-6b52-6738-761181204567@2ndquadrant.com
Diffstat (limited to 'src/backend/utils/adt/jsonpath_exec.c')
0 files changed, 0 insertions, 0 deletions