Re: closesocket behavior in different platforms - Mailing list pgsql-hackers

From Amit Kapila
Subject Re: closesocket behavior in different platforms
Date
Msg-id CAA4eK1K0U96kPeuni-V2EjfP-a8mMxo1tQ2B1TY_yG9FqPAsyA@mail.gmail.com
Whole thread Raw
In response to Re: closesocket behavior in different platforms  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: closesocket behavior in different platforms  (Amit Kapila <amit.kapila16@gmail.com>)
List pgsql-hackers
On Wed, Jan 29, 2020 at 8:29 PM Robert Haas <robertmhaas@gmail.com> wrote:
>
> On Wed, Jan 29, 2020 at 6:04 AM vignesh C <vignesh21@gmail.com> wrote:
> > Thanks for your review and suggestion. I have made a patch based on
> > similar lines. Attached patch has the doc update with the explanation.
> > Thoughts?
>
> Documenting this doesn't seem very useful to me.
>

I thought of documenting it because this has been reported/discussed
multiple times (see some of the links of discussions at the end of the
first email) and every time we need to spend time explaining the same
thing.  However, if we decide not to do that I am fine with it.

> If we could fix the
> code, that would be useful, but otherwise I think I'd just do nothing.
>

Yeah, that is our first choice as well, but there doesn't seem to be a
good solution to it as this is a platform-specific behavior.

-- 
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com



pgsql-hackers by date:

Previous
From: Craig Ringer
Date:
Subject: Re: Do we need to handle orphaned prepared transactions in the server?
Next
From: Kyotaro Horiguchi
Date:
Subject: Re: pg_stat_progress_basebackup - progress reporting forpg_basebackup, in the server side