Re: logical replication - still unstable after all these months

From: Mark Kirkwood <mark(dot)kirkwood(at)catalyst(dot)net(dot)nz>
To: Erik Rijkers <er(at)xs4all(dot)nl>
Cc: Petr Jelinek <petr(dot)jelinek(at)2ndquadrant(dot)com>, Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
Subject: Re: logical replication - still unstable after all these months
Date: 2017-06-02 06:55:46
Message-ID: 896cf6cc-ba08-2433-d9ef-f8ca1f3853f7@catalyst.net.nz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 02/06/17 17:11, Erik Rijkers wrote:

> On 2017-06-02 00:46, Mark Kirkwood wrote:
>> On 31/05/17 21:16, Petr Jelinek wrote:
>>
>> I'm seeing a new failure with the patch applied - this time the
>> history table has missing rows. Petr, I'll put back your access :-)
>
> Is this error during 1-minute runs?
>
> I'm asking because I've moved back to longer (1-hour) runs (no errors
> so far), and I'd like to keep track of what the most 'vulnerable'
> parameters are.
>

Yeah, still using your test config (with my minor modifications).

When I got the error the 1st time, I did a complete make clean and
rebuild....but it is still possible I've 'done it wrong' - so
independent confirmation would be good!

Cheers

Mark

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Magnus Hagander 2017-06-02 07:41:35 Re: Fix a typo in predicate.c
Previous Message Noah Misch 2017-06-02 06:32:16 Re: [PATCH] Fixed malformed error message on malformed SCRAM message.