Re: Problem with logical replication (crash with REPLICA IDENTITYFULL and cascading replication) - Mailing list pgsql-hackers

From Justin Pryzby
Subject Re: Problem with logical replication (crash with REPLICA IDENTITYFULL and cascading replication)
Date
Msg-id 20200417002727.GU2228@telsasoft.com
Whole thread Raw
In response to Problem with logical replication  (Dilip Kumar <dilipbalaut@gmail.com>)
List 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"
"CREATEPUBLICATION 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'
PUBLICATIONmypub"
 
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



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Poll: are people okay with function/operator table redesign?
Next
From: Michael Paquier
Date:
Subject: Re: Do we need to handle orphaned prepared transactions in theserver?