Re: closesocket behavior in different platforms

Поиск
Список
Период
Сортировка
От Amit Kapila
Тема Re: closesocket behavior in different platforms
Дата
Msg-id CAA4eK1K0U96kPeuni-V2EjfP-a8mMxo1tQ2B1TY_yG9FqPAsyA@mail.gmail.com
обсуждение исходный текст
Ответ на Re: closesocket behavior in different platforms  (Robert Haas <robertmhaas@gmail.com>)
Ответы Re: closesocket behavior in different platforms
Список 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 по дате отправления:

Предыдущее
От: Craig Ringer
Дата:
Сообщение: Re: Do we need to handle orphaned prepared transactions in the server?
Следующее
От: Kyotaro Horiguchi
Дата:
Сообщение: Re: pg_stat_progress_basebackup - progress reporting forpg_basebackup, in the server side