pg.ddx.io  pgsql-committers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
pgsql: Fix a WARNING for data origin discrepancies.
3+ messages / 1 participants
[nested] [flat]

* pgsql: Fix a WARNING for data origin discrepancies.
@ 2025-02-21 09:17 Amit Kapila <akapila@postgresql.org>
  0 siblings, 0 replies; 3+ messages in thread

From: Amit Kapila @ 2025-02-21 09:17 UTC (permalink / raw)
  To: pgsql-committers@lists.postgresql.org

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

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/b4e0d0c53fabe7d19b6a081d6c2b98aa4df55295

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(-)



^ permalink  raw  reply  [nested|flat] 3+ messages in thread

* pgsql: Fix a WARNING for data origin discrepancies.
@ 2025-02-21 09:17 Amit Kapila <akapila@postgresql.org>
  0 siblings, 0 replies; 3+ messages in thread

From: Amit Kapila @ 2025-02-21 09:17 UTC (permalink / raw)
  To: pgsql-committers@lists.postgresql.org

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

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(-)



^ permalink  raw  reply  [nested|flat] 3+ messages in thread

* pgsql: Fix a WARNING for data origin discrepancies.
@ 2025-02-21 09:17 Amit Kapila <akapila@postgresql.org>
  0 siblings, 0 replies; 3+ messages in thread

From: Amit Kapila @ 2025-02-21 09:17 UTC (permalink / raw)
  To: pgsql-committers@lists.postgresql.org

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

Branch
------
REL_16_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/1c2a2354c3848d9f03dc627270bdca073a5a37bc

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(-)



^ permalink  raw  reply  [nested|flat] 3+ messages in thread


end of thread, other threads:[~2025-02-21 09:17 UTC | newest]

Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2025-02-21 09:17 pgsql: Fix a WARNING for data origin discrepancies. Amit Kapila <akapila@postgresql.org>
2025-02-21 09:17 pgsql: Fix a WARNING for data origin discrepancies. Amit Kapila <akapila@postgresql.org>
2025-02-21 09:17 pgsql: Fix a WARNING for data origin discrepancies. Amit Kapila <akapila@postgresql.org>

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox