Re: logical replication - still unstable after all these months

From: Erik Rijkers <er(at)xs4all(dot)nl>
To: Mark Kirkwood <mark(dot)kirkwood(at)catalyst(dot)net(dot)nz>
Cc: 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-27 08:44:24
Message-ID: 567473bdceed61ff30f63a3350468f31@xs4all.nl
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2017-05-27 10:30, Erik Rijkers wrote:
> On 2017-05-27 01:35, Mark Kirkwood wrote:

> Here is what I have:
>
> instances.sh:
> testset.sh
> pgbench_derail2.sh
> pubsub.sh

To be clear:

( Apart from that standalone call like
./pgbench_derail2.sh $scale $clients $duration $date_str
)

I normally run by editing the parameters in testset.sh, then run:

./testset.sh

that then shows a tail -F of the output-logfile (to paste into another
screen).

in yet another screen the 'watch -n20 results.sh' line

The output=files are the .txt files.
The logfiles of the instances are (at the end of each test) copied to
directory logfiles/
under a meaningful name that shows the parameters, and with an extension
like '.ok.log' or '.NOK.log'.

I am very curious at your results.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2017-05-27 10:13:19 Re: logical replication - still unstable after all these months
Previous Message Erik Rijkers 2017-05-27 08:30:23 Re: logical replication - still unstable after all these months