| From: | Amit Kapila <akapila(at)postgresql(dot)org> |
|---|---|
| To: | pgsql-committers(at)lists(dot)postgresql(dot)org |
| Subject: | pgsql: Refactor pgoutput_change(). |
| Date: | 2023-03-30 05:56:58 |
| Message-ID: | E1phlHM-000QLs-S0@gemulon.postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
Refactor pgoutput_change().
Instead of mostly-duplicate code for different operation
(insert/update/delete) types, write a common code to compute old/new
tuples, and check the row filter.
Author: Hou Zhijie
Reviewed-by: Peter Smith, Amit Kapila
Discussion: https://postgr.es/m/OS0PR01MB5716194A47FFA8D91133687D94BF9@OS0PR01MB5716.jpnprd01.prod.outlook.com
Branch
------
master
Details
-------
https://git.postgresql.org/pg/commitdiff/da324d6cd45bbbcc1682cc2fcbc4f575281916af
Modified Files
--------------
src/backend/replication/pgoutput/pgoutput.c | 235 ++++++++++------------------
1 file changed, 79 insertions(+), 156 deletions(-)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2023-03-30 06:38:25 | pgsql: Fix incorrect format placeholders |
| Previous Message | David Rowley | 2023-03-30 03:37:30 | pgsql: Fix outdated comments regarding TupleTableSlots |