pg.ddx.io pgsql-bugs@postgresql.org mailing list archive
help / color / mirror / Atom feed From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andres Freund <andres@anarazel.de>
Cc: pgsql-bugs@lists.postgresql.org, David Rowley <dgrowleyml@gmail.com>
Cc: Fabien COELHO <coelho@cri.ensmp.fr>
Cc: Jawarilal, Manish <Manish.Jawarilal@dell.com>
Subject: Re: pgbench bug / limitation
Date: Fri, 05 Jun 2020 13:32:35 -0400
Message-ID: <1509305.1591378355@sss.pgh.pa.us> (raw )
In-Reply-To: <D973F4AF-8949-42C1-ABF1-E87F7C63E746@anarazel.de >
References: <BL0PR1901MB1985F219C46C61EDE7036C34ED8E0@BL0PR1901MB1985.namprd19.prod.outlook.com >
<7221.1590687090@sss.pgh.pa.us >
<BL0PR1901MB1985A8B4D3E5B39E32A9EA55ED8F0@BL0PR1901MB1985.namprd19.prod.outlook.com >
<10327.1590763515@sss.pgh.pa.us >
<BL0PR1901MB198583EAC6C8A3B770D20F1AED8A0@BL0PR1901MB1985.namprd19.prod.outlook.com >
<384920.1591027137@sss.pgh.pa.us >
<CAApHDvrjWtJa9oQ98oH+9PCvTgOkGZP+gcmottNX95sjn6o9fQ@mail.gmail.com >
<512846.1591057287@sss.pgh.pa.us >
<CAApHDvpMEAaZMxtzixbnb7ySo=Kb1eUfshEB-y4YOm8SgGrpiw@mail.gmail.com >
<alpine.DEB.2.22.394.2006021258170.87735@pseudo >
<CAApHDvpDBkjj6a+Ld-9YGW=_Bcxss8Yyz_QYjtjus3WUsTb+1g@mail.gmail.com >
<1507639.1591375547@sss.pgh.pa.us >
<D973F4AF-8949-42C1-ABF1-E87F7C63E746@anarazel.de >
Andres Freund <andres@anarazel.de> writes:
> 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.
> IIRC WaitForMultiple* only supports 64 objects or such. Which might be problematic here.
Ugh, so it does. I'd also just noted that its timeout resolution is
only in msec, which is exactly why we want to use ppoll() not poll()
here on Unix-oid OS's. So WaitForMultipleObjects() is out.
I still suppose that select(2) is not a native API for Windows. Since
we know that it can be made to support more than 64 FDs, it must not
be built on top of WaitForMultipleObjects ... but then what *is* it
built on?
regards, tom lane
view thread (26+ messages) latest in thread
Message-ID: <1509305.1591378355@sss.pgh.pa.us>
Permalink: ../1509305.1591378355@sss.pgh.pa.us/
Also on: postgresql.org/message-id/1509305.1591378355@sss.pgh.pa.us
copy link · copy postgr.es
reply Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, andres@anarazel.de, dgrowleyml@gmail.com, coelho@cri.ensmp.fr, Manish.Jawarilal@dell.com
Subject: Re: pgbench bug / limitation
In-Reply-To: <1509305.1591378355@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox