Re: pgbench bug / limitation
От | Andres Freund |
---|---|
Тема | Re: pgbench bug / limitation |
Дата | |
Msg-id | D973F4AF-8949-42C1-ABF1-E87F7C63E746@anarazel.de обсуждение исходный текст |
Ответ на | Re: pgbench bug / limitation (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: pgbench bug / limitation
|
Список | pgsql-bugs |
Hi, On June 5, 2020 9:45:47 AM PDT, Tom Lane <tgl@sss.pgh.pa.us> wrote: >The idea that I vaguely had was to build our own array of socket FDs >(bypassing the unnecessary de-duplication logic in FD_SET) and then >call >WaitForMultipleObjects() or similar directly. This would of course >be quite Windows-specific, which'd be annoying, but it seems like >getting out of using select() on Windows wouldn't be a bad thing. >Trying to make the same code work with two basically different models >of what a fd_set is seems like a recipe for pain. This would also get >us out from under the hack of redefining FD_SETSIZE. IIRC WaitForMultiple* only supports 64 objects or such. Which might be problematic here. Andres -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
В списке pgsql-bugs по дате отправления: