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.tatarint...@postgrespro.ru> Author: Hou Zhijie <houzj.f...@fujitsu.com> Author: Shlok Kyal <shlok.kyal....@gmail.com> Reviewed-by: Vignesh C <vignes...@gmail.com> Reviewed-by: Amit Kapila <amit.kapil...@gmail.com> Backpatch-through: 16, where it was introduced Discussion: https://postgr.es/m/5eda6a9c-63cf-404d-8a49-8dcb116a2...@postgrespro.ru Branch ------ REL_17_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/0ae1245e04ad7130238acf8cfb6d40c32fa1e588 Modified Files -------------- doc/src/sgml/ref/create_subscription.sgml | 12 +-- src/backend/commands/subscriptioncmds.c | 15 ++-- src/test/subscription/t/030_origin.pl | 120 +++++++++++++++++++++++++++++- 3 files changed, 133 insertions(+), 14 deletions(-)
