From: | Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com> |
---|---|
To: | tgl(at)sss(dot)pgh(dot)pa(dot)us |
Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: GSSENC'ed connection stalls while reconnection attempts. |
Date: | 2020-07-15 02:49:06 |
Message-ID: | 20200715.114906.748203293592936776.horikyota.ntt@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
At Tue, 14 Jul 2020 13:31:31 +0900 (JST), Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com> wrote in
> Agreed to separate the change from this issue. I also don't think
> that change in behavior dramatically improve the situation since we
> should have had a bunch of trouble when a write actually failed in the
> normal case.
>
> I'm going to post a patch to change the comment of pqPacketSend.
So this is a proposal to add a description about the behavior on write
failure. The last half of the addition is a copy from the comment of
pqFlush.
regards.
--
Kyotaro Horiguchi
NTT Open Source Software Center
Attachment | Content-Type | Size |
---|---|---|
0001-Explain-pqPacketSend-more-precisely.patch | text/x-patch | 1.3 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Amit Kapila | 2020-07-15 02:51:00 | Re: Parallel Seq Scan vs kernel read ahead |
Previous Message | Andres Freund | 2020-07-15 02:47:53 | Re: Binary support for pgoutput plugin |