Re: [HACKERS] logical replication - still unstable after all thesemonths - Mailing list pgsql-hackers

From Mark Kirkwood
Subject Re: [HACKERS] logical replication - still unstable after all thesemonths
Date
Msg-id 3ac93e64-d7a2-d82c-b0c2-6022a3d59f12@catalyst.net.nz
Whole thread Raw
In response to Re: [HACKERS] logical replication - still unstable after all thesemonths  (Petr Jelinek <petr.jelinek@2ndquadrant.com>)
Responses Re: [HACKERS] logical replication - still unstable after all thesemonths  (Petr Jelinek <petr.jelinek@2ndquadrant.com>)
List pgsql-hackers
On 29/05/17 23:14, Petr Jelinek wrote:

> On 29/05/17 03:33, Jeff Janes wrote:
>
>> What would you want to look at?  Would saving the WAL from the master be
>> helpful?
>>
> Useful info is, logs from provider (mainly the logical decoding logs
> that mention LSNs), logs from subscriber (the lines about when sync
> workers finished), contents of the pg_subscription_rel (with srrelid
> casted to regclass so we know which table is which), and pg_waldump
> output around the LSNs found in the logs and in the pg_subscription_rel
> (+ few lines before and some after to get context). It's enough to only
> care about LSNs for the table(s) that are out of sync.
>

I have a run that aborted with failure (accounts table md5 mismatch). 
Petr - would you like to have access to the machine ? If so send me you 
public key and I'll set it up.

Cheers

Mark



pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: [HACKERS] Bug when dumping "empty" operator classes
Next
From: Tom Lane
Date:
Subject: Re: [HACKERS] pg_resetwal is broken if run from v10 against older version of PG data directory