From: | Andres Freund <andres(at)anarazel(dot)de> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org,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> |
Subject: | Re: logical replication busy-waiting on a lock |
Date: | 2017-05-27 15:17:19 |
Message-ID: | 5869C803-9AAA-4B81-AED4-2177A114FC9A@anarazel.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On May 27, 2017 9:48:22 AM EDT, Petr Jelinek <petr(dot)jelinek(at)2ndquadrant(dot)com> wrote:
>Actually, I guess it's the pid 47457 (COPY process) who is actually
>running the xid 73322726. In that case that's the same thing Masahiko
>Sawada reported [1]. Which basically is result of snapshot builder
>waiting for transaction to finish, that's normal if there is a long
>transaction running when the snapshot is being created (and the COPY is
>a long transaction).
Hm. I suspect the issue is that the exported snapshot needs an xid for some crosscheck, and that's what we're waiting for. Could you check what happens if you don't assign one and just content the error checks out? Not at my computer, just theorizing.
Andres
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
From | Date | Subject | |
---|---|---|---|
Next Message | Erik Rijkers | 2017-05-27 16:12:46 | Re: logical replication - still unstable after all these months |
Previous Message | Andres Freund | 2017-05-27 15:11:46 | Re: logical replication - still unstable after all these months |