| From: | Mark Kirkwood <mark(dot)kirkwood(at)catalyst(dot)net(dot)nz> |
|---|---|
| To: | Petr Jelinek <petr(dot)jelinek(at)2ndquadrant(dot)com>, Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
| Cc: | Erik Rijkers <er(at)xs4all(dot)nl>, pgsql-hackers <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-29 21:06:48 |
| Message-ID: | 3ac93e64-d7a2-d82c-b0c2-6022a3d59f12@catalyst.net.nz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2017-05-29 21:06:49 | Re: [PATCH] Fixed malformed error message on malformed SCRAM message. |
| Previous Message | Michael Paquier | 2017-05-29 21:01:12 | Re: Bug when dumping "empty" operator classes |