Re: WL_SOCKET_ACCEPT fairness on Windows - Mailing list pgsql-hackers

From Jonathan S. Katz
Subject Re: WL_SOCKET_ACCEPT fairness on Windows
Date
Msg-id 3c0701d9-9758-b8d9-5e01-abc784b7c086@postgresql.org
Whole thread Raw
In response to Re: WL_SOCKET_ACCEPT fairness on Windows  (Thomas Munro <thomas.munro@gmail.com>)
Responses Re: WL_SOCKET_ACCEPT fairness on Windows
List pgsql-hackers
On 3/31/23 11:00 PM, Thomas Munro wrote:

>>> I mention this now because I'm not sure whether to consider this an
>>> 'open item' for 16, or merely an enhancement for 17.  I guess the
>>> former, because someone might call that a new denial of service
>>> vector.  On the other hand, if you fill up the listen queue for socket
>>> 1 with enough vigour, you're also denying service to socket 1, so I
>>> don't know if it's worth worrying about.  Opinions on that?
>>
>> I'm not sure either. It doesn't strike me as a particularly relevant
>> bottleneck. And the old approach of doing more work for every single
>> connection also made many connections worse, I think?
> 
> Alright, let's see if anyone else thinks this is worth fixing for 16.

[RMT hat]

Given this has sat for a bit, I wanted to see if any of your thinking 
has changed on whether this should be fixed for v16 or v17. I have 
personally not formed an opinion yet, but per the current discussion, it 
seems like this could wait?

Thanks,

Jonathan


Attachment

pgsql-hackers by date:

Previous
From: "Jonathan S. Katz"
Date:
Subject: Re: pg_stat_io not tracking smgrwriteback() is confusing
Next
From: Alexander Lakhin
Date:
Subject: Re: benchmark results comparing versions 15.2 and 16