| From: | Mark Kirkwood <mark(dot)kirkwood(at)catalyst(dot)net(dot)nz> |
|---|---|
| To: | Erik Rijkers <er(at)xs4all(dot)nl> |
| 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-28 22:17:49 |
| Message-ID: | 7bcbe906-b48c-3808-28a3-5fa9949a85a7@catalyst.net.nz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 28/05/17 19:01, Mark Kirkwood wrote:
>
> So running in cloud land now...so for no errors - will update.
>
>
>
The framework ran 600 tests last night, and I see 3 'NOK' results, i.e 3
failed test runs (all scale 25 and 8 pgbench clients). Given the way the
test decides on failure (gets tired of waiting for the table md5's to
match) - it begs the question 'What if it had waited a bit longer'?
However from what I can see in all cases:
- the rowcounts were the same in master and replica
- the md5 of pgbench_accounts was different
...so does seem possible that there is some bug being tickled here.
Unfortunately the test framework blasts away the failed tables and
subscription and continues on...I'm going to amend it to stop on failure
so I can have a closer look at what happened.
regards
Mark
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Janes | 2017-05-29 01:33:51 | Re: logical replication - still unstable after all these months |
| Previous Message | Tom Lane | 2017-05-28 21:16:24 | Inconsistent syntax for NumericOnly grammar production |