Re: logical replication - still unstable after all these months

From: Erik Rijkers <er(at)xs4all(dot)nl>
To: Simon Riggs <simon(at)2ndquadrant(dot)com>
Cc: 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 08:09:56
Message-ID: 2c873422954d8847be37bee25a40c73d@xs4all.nl
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2017-05-26 09:40, Simon Riggs wrote:
>
> If we can find out what the bug is with a repeatable test case we can
> fix it.
>
> Could you provide more details? Thanks

I will, just need some time to clean things up a bit.

But what I would like is for someone else to repeat my 100x1-minute
tests, taking as core that snippet I posted in my previous email. I
built bash-stuff around that core (to take md5's, shut-down/start-up the
two instances between runs, write info to log-files, etc). But it would
be good if someone else made that separately because if that then does
not fail, it would prove that my test-harness is at fault (and not
logical replication).

The idea is simple enough:

startup instance1
startup instance2 (on same machine)
primary: init pgbench tables
primary: add primary key to pgbench_history
copy empty tables to replica by dump/restore
primary: start publication
replica: start subscription
primary: run 1-minute pgbench
wait till the 4 md5's of primary pgbench tables
are the same as the 4 md5's of replica pgbench
tables (this will need a time-out).
log 'ok' or 'not ok'
primary: clean up publication
replica: clean up subscription
shutdown primary
shutdown replica

this whole thing 100x

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Mark Kirkwood 2017-05-26 08:29:15 Re: logical replication - still unstable after all these months
Previous Message Nguyen Le Hoang Kha 2017-05-26 08:04:20 Extra Vietnamese unaccent rules