From: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
---|---|
To: | David Rowley <dgrowleyml(at)gmail(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Jawarilal, Manish" <Manish(dot)Jawarilal(at)dell(dot)com>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
Subject: | Re: pgbench bug / limitation |
Date: | 2020-06-05 04:44:33 |
Message-ID: | alpine.DEB.2.22.394.2006050637420.213031@pseudo |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Hello David,
> On Tue, 2 Jun 2020 at 23:27, Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> wrote:
>> Attached is a blind attempt at working around the issue based on what you
>> show below, that I cannot test.
>
> I suppose we might be able to do something like that. It does expose
> us to the implementation of Microsoft's fd_set struct, but surely the
> shape of that must be pretty much fixed since if it were to be changed
> then software that's already compiled would break.
Yep. I cannot seen how to do it without some assumption about the
underlying implementation. I agree that it breaks the very principle of
the interface, which is to hide fdset implementation details.
> I tested the patch on a Windows machine
Thanks.
> and it seems to work.
Good.
> I'm not much a fan of the naming of the new macro though. Wouldn't it
> be better to reverse the logic and call it IS_VALID_FD?
I hesitated. Here it is with a inversion/renaming, and a check that fd is
positive on windows. I renamed to "FD_IS_VALID" which seems to read
better.
--
Fabien.
Attachment | Content-Type | Size |
---|---|---|
pgbench-select-win-2.patch | text/x-diff | 864 bytes |
From | Date | Subject | |
---|---|---|---|
Next Message | David G. Johnston | 2020-06-05 05:07:13 | Re: BUG #16480: Spool query with results. |
Previous Message | David Rowley | 2020-06-05 04:10:34 | Re: pgbench bug / limitation |