From: | Andres Freund <andres(at)anarazel(dot)de> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-hackers(at)postgreSQL(dot)org |
Subject: | Re: Apparent walsender bug triggered by logical replication |
Date: | 2017-06-30 00:15:33 |
Message-ID: | 20170630001533.f7yhwnq6qi5kl2et@alap3.anarazel.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi,
On 2017-06-29 20:07:14 -0400, Tom Lane wrote:
> I was able to make the hang go away by means of the attached patch that
> allows WalSndWaitForWal to exit early if the client has shut down the
> COPY. However, since that function is miserably underdocumented (like
> most of this code :-(), I have little idea if this is correct or safe.
Seems reasonable to me.
> I also wonder why WalSndWaitForWal is being called for WAL that seemingly
> doesn't exist yet, and whether that doesn't indicate another bug somewhere
> in this stack.
That's pretty normal - we can only send back something once a
transaction is complete, and until that happens we'll just block waiting
for more WAL.
Greetings,
Andres Freund
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2017-06-30 00:56:34 | Re: Broken hint bits (freeze) |
Previous Message | Tom Lane | 2017-06-30 00:07:14 | Apparent walsender bug triggered by logical replication |