summaryrefslogtreecommitdiff
path: root/meson.build
diff options
context:
space:
mode:
authorAmit Kapila2025-07-24 08:36:31 +0000
committerAmit Kapila2025-07-24 08:38:01 +0000
commit967309116f0d2cda20228229b2fd212948fd0385 (patch)
tree237dfe529f2ec94292346baf4e74b09f8dff0dd2 /meson.build
parent635a856279ef55074dfc7a2a96c7fd686b5ff015 (diff)
Fix duplicate transaction replay during pg_createsubscriber.REL_17_STABLE
Previously, the tool could replay the same transaction twice, once during recovery, then again during replication after the subscriber was set up. This occurred because the same recovery_target_lsn was used both to finalize recovery and to start replication. If recovery_target_inclusive = true, the transaction at that LSN would be applied during recovery and then sent again by the publisher leading to duplication. To prevent this, we now set recovery_target_inclusive = false. This ensures the transaction at recovery_target_lsn is not reapplied during recovery, avoiding duplication when replication begins. Bug #18897 Reported-by: Zane Duffield <duffieldzane@gmail.com> Author: Shlok Kyal <shlok.kyal.oss@gmail.com> Reviewed-by: vignesh C <vignesh21@gmail.com> Reviewed-by: Amit Kapila <amit.kapila16@gmail.com> Backpatch-through: 17, where it was introduced Discussion: https://postgr.es/m/18897-d3db67535860dddb@postgresql.org
Diffstat (limited to 'meson.build')
0 files changed, 0 insertions, 0 deletions