| From: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
|---|---|
| To: | tushar <tushar(dot)ahuja(at)enterprisedb(dot)com> |
| Cc: | Erik Rijkers <er(at)xs4all(dot)nl>, Simon Riggs <simon(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, pgsql-hackers-owner(at)postgresql(dot)org |
| Subject: | Re: logical replication - still unstable after all these months |
| Date: | 2017-05-26 19:07:50 |
| Message-ID: | CAMkU=1whG4nR726-vEU25m_uhWf60LpPh0riMQXVXhcjFL2jyA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, May 26, 2017 at 5:17 AM, tushar <tushar(dot)ahuja(at)enterprisedb(dot)com>
wrote:
>
> 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)
Hi Tushar,
pgbench starts out by truncating pgbench_history. That truncation does not
get replicated to the subscriber. The later inserts do. So your
subscriber ends up with about twice as many rows.
Cheers,
Jeff
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Regina Obe | 2017-05-26 19:14:37 | Re: PostgreSQL 10 changes in exclusion constraints - did something change? CASE WHEN behavior oddity |
| Previous Message | Amit Kapila | 2017-05-26 18:39:48 | Re: Broken hint bits (freeze) |