Re: Problem with logical replication (crash with REPLICA IDENTITY FULL and cascading replication)
Justin Pryzby <pryzby@telsasoft.com>
From: Justin Pryzby <pryzby@telsasoft.com>
To: Dilip Kumar <dilipbalaut@gmail.com>
Cc: pgsql-hackers@postgresql.org, Peter Eisentraut <peter_e@gmx.net>, Petr Jelinek <petr@2ndquadrant.com>
Date: 2020-04-17T00:27:27Z
Lists: pgsql-hackers
Confirmed and added to opened items - this is a live bug back to v10. for a in data data1; do ./tmp_install/usr/local/pgsql/bin/initdb -D $a --no-sync& done; wait echo "wal_level = logical">> data/postgresql.conf; echo "port=5433" >> data1/postgresql.conf for a in data data1; do ./tmp_install/usr/local/pgsql/bin/postmaster -D $a& done for a in "CREATE TABLE pgbench_accounts(a int primary key, b int)" "ALTER TABLE pgbench_accounts REPLICA IDENTITY FULL" "CREATE PUBLICATION mypub FOR TABLE pgbench_accounts"; do \ for p in 5432 5433; do psql -d postgres -h /tmp -p "$p" -c "$a"; done; done psql -d postgres -h /tmp -p 5433 -c "CREATE SUBSCRIPTION mysub CONNECTION 'host=127.0.0.1 port=5432 dbname=postgres' PUBLICATION mypub" psql -d postgres -h /tmp -p 5432 -c "insert into pgbench_accounts values(1,2); update pgbench_accounts set b=30 where a=1;" -- Justin
Commits
-
Fix assertion with relation using REPLICA IDENTITY FULL in subscriber
- 3acb30b49818 10.14 landed
- 70ae82b9b4b5 11.9 landed
- b4ded2f227f3 12.4 landed
- 7ccb2f54d9f3 13.0 landed