diff options
| author | Amit Kapila <akapila@postgresql.org> | 2022-12-02 10:52:08 +0530 |
|---|---|---|
| committer | Amit Kapila <akapila@postgresql.org> | 2022-12-02 10:52:58 +0530 |
| commit | 40b1491357a4a092ea054176944cf76e2fe3eff8 (patch) | |
| tree | 5ccf254873197f5e957216b6b119f9da273961df /src/backend/executor/nodeModifyTable.c | |
| parent | 069de07eae7328f13be40f1f3988448639c04285 (diff) | |
| download | postgresql-40b1491357a4a092ea054176944cf76e2fe3eff8.tar.gz postgresql-40b1491357a4a092ea054176944cf76e2fe3eff8.zip | |
Fix incorrect output from pgoutput when using column lists.
For Updates and Deletes, we were not honoring the columns list for old
tuple values while sending tuple data via pgoutput. This results in
pgoutput emitting more columns than expected.
This is not a problem for built-in logical replication as we simply ignore
additional columns based on the relation information sent previously which
didn't have those columns. However, some other users of pgoutput plugin
may expect the columns as per the column list. Also, sending extra columns
unnecessarily consumes network bandwidth defeating the purpose of the
column list feature.
Reported-by: Gunnar Morling
Author: Hou Zhijie
Reviewed-by: Amit Kapila
Backpatch-through: 15
Discussion: https://postgr.es/m/CADGJaX9kiRZ-OH0EpWF5Fkyh1ZZYofoNRCrhapBfdk02tj5EKg@mail.gmail.com
Diffstat (limited to 'src/backend/executor/nodeModifyTable.c')
0 files changed, 0 insertions, 0 deletions