aboutsummaryrefslogtreecommitdiff
path: root/contrib/postgres_fdw/postgres_fdw.c
diff options
context:
space:
mode:
authorAmit Kapila <akapila@postgresql.org>2023-01-30 08:02:08 +0530
committerAmit Kapila <akapila@postgresql.org>2023-01-30 08:02:08 +0530
commit1e8b61735cfb1a4feb72cb9ea83db690fedbfef1 (patch)
tree480c77fb6007f535c8f20301954e483de1672ad6 /contrib/postgres_fdw/postgres_fdw.c
parent8d2c1913ed3df9384973399deeb75fc1e55943fe (diff)
downloadpostgresql-1e8b61735cfb1a4feb72cb9ea83db690fedbfef1.tar.gz
postgresql-1e8b61735cfb1a4feb72cb9ea83db690fedbfef1.zip
Rename GUC logical_decoding_mode to logical_replication_mode.
Rename the developer option 'logical_decoding_mode' to the more flexible name 'logical_replication_mode' because doing so will make it easier to extend this option in the future to help test other areas of logical replication. Currently, it is used on the publisher side to allow streaming or serializing each change in logical decoding. In the upcoming patch, we are planning to use it on the subscriber. On the subscriber, it will allow serializing the changes to file and notifies the parallel apply workers to read and apply them at the end of the transaction. We discussed exposing this parameter as a subscription option but it did not seem advisable since it is primarily used for testing/debugging and there is no other such parameter. We also discussed having separate GUCs for publisher and subscriber but for current testing/debugging requirements, one GUC is sufficient. Author: Hou Zhijie Reviewed-by: Peter Smith, Kuroda Hayato, Sawada Masahiko, Amit Kapila Discussion: https://postgr.es/m/CAD21AoAy2c=Mx=FTCs+EwUsf2kQL5MmU3N18X84k0EmCXntK4g@mail.gmail.com Discussion: https://postgr.es/m/CAA4eK1+wyN6zpaHUkCLorEWNx75MG0xhMwcFhvjqm2KURZEAGw@mail.gmail.com
Diffstat (limited to 'contrib/postgres_fdw/postgres_fdw.c')
0 files changed, 0 insertions, 0 deletions