| From: | "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org> |
|---|---|
| To: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: WL_SOCKET_ACCEPT fairness on Windows |
| Date: | 2023-05-16 21:11:29 |
| Message-ID: | 3f0b4c6b-e6d1-9641-9ec8-e5a92d8b0ef2@postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 5/16/23 4:41 PM, Thomas Munro wrote:
> On Wed, May 17, 2023 at 2:57 AM Jonathan S. Katz <jkatz(at)postgresql(dot)org> wrote:
>> 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?
>
> Yeah. No one seems to think this is worth worrying about (please
> speak up if you do). I'll go ahead and remove this from the open item
> lists now, but I'll leave the patch in the CF for 17, to see if a
> Windows hacker/tester thinks it's a worthwhile improvement.
[RMT hat, personal opinion]
That seems reasonable to me.
Thanks,
Jonathan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2023-05-16 21:52:00 | Re: issue with meson builds on msys2 |
| Previous Message | Melanie Plageman | 2023-05-16 21:10:25 | Re: Memory leak from ExecutorState context? |