Re: pgsql: Add kqueue(2) support to the WaitEventSet API.
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: Thomas Munro <thomas.munro@gmail.com>, Rémi Zara <remi_zara@mac.com>, Michael Paquier <michael@paquier.xyz>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2020-02-24T21:01:41Z
Lists: pgsql-hackers
Alvaro Herrera <alvherre@2ndquadrant.com> writes: > On 2020-Feb-24, Tom Lane wrote: >> I don't think there's much point in telling Windows users about >> _setmaxstdio() here. > Yeah, telling users to _setmaxstdio() themselves is useless, because > they can't do it; that's something *we* should do. I think the 512 > limit is a bit low; why not increase that a little bit? Maybe just to > the Linux default of 1024. > Then again, that would be akin to setrlimit() on Linux. Maybe we can > consider that a separate GUC, in a separate patch, with a > platform-specific default value that just corresponds to the OS's > default, and the user can set to whatever suits them; then we call > either _setmaxstdio() or setrlimit(). Why not just drive it off max_files_per_process? On Unix, that largely exists to override the ulimit setting anyway. With no comparable knob on a Windows system, we might as well just say that's what you set. regards, tom lane
Commits
-
Don't use EV_CLEAR for kqueue events.
- 9b8aa0929390 13.0 cited
-
Fix kqueue support under debugger on macOS.
- 7bc84a1f304a 13.0 landed
-
Account explicitly for long-lived FDs that are allocated outside fd.c.
- 3d475515a15f 13.0 landed
-
Add kqueue(2) support to the WaitEventSet API.
- 815c2f0972c8 13.0 cited
-
Introduce WaitEventSet API.
- 98a64d0bd713 9.6.0 cited