pg.ddx.io pgsql-committers@postgresql.org mailing list archivehelp / color / mirror / Atom feed
pgsql: Invalidate relcache when changing REPLICA IDENTITY index. 6+ messages / 1 participants [nested] [flat]
* pgsql: Invalidate relcache when changing REPLICA IDENTITY index. @ 2021-11-16 04:28 Amit Kapila <akapila@postgresql.org> 0 siblings, 0 replies; 6+ messages in thread From: Amit Kapila @ 2021-11-16 04:28 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org Invalidate relcache when changing REPLICA IDENTITY index. When changing REPLICA IDENTITY INDEX to another one, the target table's relcache was not being invalidated. This leads to skipping update/delete operations during apply on the subscriber side as the columns required to search corresponding rows won't get logged. Author: Tang Haiying, Hou Zhijie Reviewed-by: Euler Taveira, Amit Kapila Backpatch-through: 10 Discussion: https://postgr.es/m/OS0PR01MB61133CA11630DAE45BC6AD95FB939@OS0PR01MB6113.jpnprd01.prod.outlook.com Branch ------ REL_13_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/63c3eeddc2db1b939e7f4fa8ad8ad0f3757232b1 Modified Files -------------- src/backend/commands/tablecmds.c | 6 +++ src/test/subscription/t/100_bugs.pl | 84 ++++++++++++++++++++++++++++++++++++- 2 files changed, 89 insertions(+), 1 deletion(-) ^ permalink raw reply [nested|flat] 6+ messages in thread
* pgsql: Invalidate relcache when changing REPLICA IDENTITY index. @ 2021-11-16 04:28 Amit Kapila <akapila@postgresql.org> 0 siblings, 0 replies; 6+ messages in thread From: Amit Kapila @ 2021-11-16 04:28 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org Invalidate relcache when changing REPLICA IDENTITY index. When changing REPLICA IDENTITY INDEX to another one, the target table's relcache was not being invalidated. This leads to skipping update/delete operations during apply on the subscriber side as the columns required to search corresponding rows won't get logged. Author: Tang Haiying, Hou Zhijie Reviewed-by: Euler Taveira, Amit Kapila Backpatch-through: 10 Discussion: https://postgr.es/m/OS0PR01MB61133CA11630DAE45BC6AD95FB939@OS0PR01MB6113.jpnprd01.prod.outlook.com Branch ------ REL_14_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/232fd72a5eab3ab429497796bce6e7da9e67ca3f Modified Files -------------- src/backend/commands/tablecmds.c | 6 +++ src/test/subscription/t/100_bugs.pl | 84 ++++++++++++++++++++++++++++++++++++- 2 files changed, 89 insertions(+), 1 deletion(-) ^ permalink raw reply [nested|flat] 6+ messages in thread
* pgsql: Invalidate relcache when changing REPLICA IDENTITY index. @ 2021-11-16 04:28 Amit Kapila <akapila@postgresql.org> 0 siblings, 0 replies; 6+ messages in thread From: Amit Kapila @ 2021-11-16 04:28 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org Invalidate relcache when changing REPLICA IDENTITY index. When changing REPLICA IDENTITY INDEX to another one, the target table's relcache was not being invalidated. This leads to skipping update/delete operations during apply on the subscriber side as the columns required to search corresponding rows won't get logged. Author: Tang Haiying, Hou Zhijie Reviewed-by: Euler Taveira, Amit Kapila Backpatch-through: 10 Discussion: https://postgr.es/m/OS0PR01MB61133CA11630DAE45BC6AD95FB939@OS0PR01MB6113.jpnprd01.prod.outlook.com Branch ------ REL_10_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/2c0443c595705b6eda1932e4b1b3debc2162986d Modified Files -------------- src/backend/commands/tablecmds.c | 6 +++ src/test/subscription/t/100_bugs.pl | 86 ++++++++++++++++++++++++++++++++++++- 2 files changed, 91 insertions(+), 1 deletion(-) ^ permalink raw reply [nested|flat] 6+ messages in thread
* pgsql: Invalidate relcache when changing REPLICA IDENTITY index. @ 2021-11-16 04:28 Amit Kapila <akapila@postgresql.org> 0 siblings, 0 replies; 6+ messages in thread From: Amit Kapila @ 2021-11-16 04:28 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org Invalidate relcache when changing REPLICA IDENTITY index. When changing REPLICA IDENTITY INDEX to another one, the target table's relcache was not being invalidated. This leads to skipping update/delete operations during apply on the subscriber side as the columns required to search corresponding rows won't get logged. Author: Tang Haiying, Hou Zhijie Reviewed-by: Euler Taveira, Amit Kapila Backpatch-through: 10 Discussion: https://postgr.es/m/OS0PR01MB61133CA11630DAE45BC6AD95FB939@OS0PR01MB6113.jpnprd01.prod.outlook.com Branch ------ REL_12_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/9816e2d3182681f0cdd31b5b0d15cfb2d62cc784 Modified Files -------------- src/backend/commands/tablecmds.c | 6 +++ src/test/subscription/t/100_bugs.pl | 86 ++++++++++++++++++++++++++++++++++++- 2 files changed, 91 insertions(+), 1 deletion(-) ^ permalink raw reply [nested|flat] 6+ messages in thread
* pgsql: Invalidate relcache when changing REPLICA IDENTITY index. @ 2021-11-16 04:28 Amit Kapila <akapila@postgresql.org> 0 siblings, 0 replies; 6+ messages in thread From: Amit Kapila @ 2021-11-16 04:28 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org Invalidate relcache when changing REPLICA IDENTITY index. When changing REPLICA IDENTITY INDEX to another one, the target table's relcache was not being invalidated. This leads to skipping update/delete operations during apply on the subscriber side as the columns required to search corresponding rows won't get logged. Author: Tang Haiying, Hou Zhijie Reviewed-by: Euler Taveira, Amit Kapila Backpatch-through: 10 Discussion: https://postgr.es/m/OS0PR01MB61133CA11630DAE45BC6AD95FB939@OS0PR01MB6113.jpnprd01.prod.outlook.com Branch ------ REL_11_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/40fb634b1a7be5cf27e0d6c391a6f8f0eb4de412 Modified Files -------------- src/backend/commands/tablecmds.c | 6 +++ src/test/subscription/t/100_bugs.pl | 86 ++++++++++++++++++++++++++++++++++++- 2 files changed, 91 insertions(+), 1 deletion(-) ^ permalink raw reply [nested|flat] 6+ messages in thread
* pgsql: Invalidate relcache when changing REPLICA IDENTITY index. @ 2021-11-16 04:28 Amit Kapila <akapila@postgresql.org> 0 siblings, 0 replies; 6+ messages in thread From: Amit Kapila @ 2021-11-16 04:28 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org Invalidate relcache when changing REPLICA IDENTITY index. When changing REPLICA IDENTITY INDEX to another one, the target table's relcache was not being invalidated. This leads to skipping update/delete operations during apply on the subscriber side as the columns required to search corresponding rows won't get logged. Author: Tang Haiying, Hou Zhijie Reviewed-by: Euler Taveira, Amit Kapila Backpatch-through: 10 Discussion: https://postgr.es/m/OS0PR01MB61133CA11630DAE45BC6AD95FB939@OS0PR01MB6113.jpnprd01.prod.outlook.com Branch ------ master Details ------- https://git.postgresql.org/pg/commitdiff/354a1f8d220fbbb07b0ded32c5ade72646afb801 Modified Files -------------- src/backend/commands/tablecmds.c | 6 +++ src/test/subscription/t/100_bugs.pl | 84 ++++++++++++++++++++++++++++++++++++- 2 files changed, 89 insertions(+), 1 deletion(-) ^ permalink raw reply [nested|flat] 6+ messages in thread
end of thread, other threads:[~2021-11-16 04:28 UTC | newest] Thread overview: 6+ messages (download: mbox mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2021-11-16 04:28 pgsql: Invalidate relcache when changing REPLICA IDENTITY index. Amit Kapila <akapila@postgresql.org> 2021-11-16 04:28 pgsql: Invalidate relcache when changing REPLICA IDENTITY index. Amit Kapila <akapila@postgresql.org> 2021-11-16 04:28 pgsql: Invalidate relcache when changing REPLICA IDENTITY index. Amit Kapila <akapila@postgresql.org> 2021-11-16 04:28 pgsql: Invalidate relcache when changing REPLICA IDENTITY index. Amit Kapila <akapila@postgresql.org> 2021-11-16 04:28 pgsql: Invalidate relcache when changing REPLICA IDENTITY index. Amit Kapila <akapila@postgresql.org> 2021-11-16 04:28 pgsql: Invalidate relcache when changing REPLICA IDENTITY index. 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