Fix a WARNING for data origin discrepancies.
authorAmit Kapila <akapila@postgresql.org>
Fri, 21 Feb 2025 08:51:29 +0000 (14:21 +0530)
committerAmit Kapila <akapila@postgresql.org>
Fri, 21 Feb 2025 08:51:29 +0000 (14:21 +0530)
commit0ae1245e04ad7130238acf8cfb6d40c32fa1e588
tree8a82c959cd33878e883682edd3aa65f3e253502c
parent2e0f93d7cb09799bff498c604e875ac2e7a2b9dc
Fix a WARNING for data origin discrepancies.

Previously, a WARNING was issued at the time of defining a subscription
with origin=NONE only when the publisher subscribed to the same table from
other publishers, indicating potential data origination from different
origins. However, the publisher can subscribe to the partition ancestors
or partition children of the table from other publishers, which could also
result in mixed-origin data inclusion. So, give a WARNING in those cases
as well.

Reported-by: Sergey Tatarintsev <s.tatarintsev@postgrespro.ru>
Author: Hou Zhijie <houzj.fnst@fujitsu.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: 16, where it was introduced
Discussion: https://postgr.es/m/5eda6a9c-63cf-404d-8a49-8dcb116a29f3@postgrespro.ru
doc/src/sgml/ref/create_subscription.sgml
src/backend/commands/subscriptioncmds.c
src/test/subscription/t/030_origin.pl