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: 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 05:11:38
Message-ID: 9041e8dd351687bdf6a24004362ea044@xs4all.nl
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

thanks,

Erik Rijkers

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Noah Misch 2017-06-02 05:21:28 Re: Race conditions with WAL sender PID lookups
Previous Message Amit Langote 2017-06-02 04:51:35 Re: BEFORE trigger can cause undetected partition constraint violation