Re: [HACKERS] logical replication - still unstable after all thesemonths
От | tushar |
---|---|
Тема | Re: [HACKERS] logical replication - still unstable after all thesemonths |
Дата | |
Msg-id | 67450f3a-6686-deea-1b0a-22d205777c4d@enterprisedb.com обсуждение исходный текст |
Ответ на | Re: [HACKERS] logical replication - still unstable after all thesemonths (Erik Rijkers <er@xs4all.nl>) |
Ответы |
Re: [HACKERS] logical replication - still unstable after all these months
|
Список | pgsql-hackers |
On 05/26/2017 12:57 PM, Erik Rijkers wrote: > The failure is that in the result state the replicated tables differ > from the original tables. I am also getting similar behavior Master= run pgbench with scaling factor =1 (./pg_bench -i -s 1 postgres ) delete rows from pgbench_history ( delete from pgbench_history) create publication (create publication pub for table pgbench_history) Slave= run pgbench with scaling factor =1 (./pg_bench -i -s 1 postgres -p 5000 ) delete rows from pgbench_history ( delete from pgbench_history) create subscription (create subscription sub connection 'dbname=postgres host=localhost user=centos) publication pub; create a test.sql file , having an insert statement [centos@centos-cpula bin]$ cat test.sql insert into pgbench_history values (1,1,1,1,now(),'anv'); now run pgbench with -T / -c / -j options First time = ./pgbench -t 5 -c 90 -j 90 -f test.sql postgres count on Master/slave are SAME . run second time = ./pgbench -T 20 -c 90 -j 90 -f test.sql postgres check the row count on master/standby Master= postgres=# select count(*) from pgbench_history ; count -------- 536836 (1 row) Standby = postgres=# select count(*) from pgbench_history ; count --------- 1090959 (1 row) -- regards,tushar EnterpriseDB https://www.enterprisedb.com/ The Enterprise PostgreSQL Company
В списке pgsql-hackers по дате отправления: