From: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | David Rowley <dgrowleyml(at)gmail(dot)com>, "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 18:17:01 |
Message-ID: | alpine.DEB.2.22.394.2006052004340.32228@pseudo |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Hello Tom,
> More to the point, this does nothing to get around the O(N^2) cost of
> adding N FDs to the fd_set with Microsoft's implementation; so I do not
> think it's really going to fix the problem for people who want to use
> lots of connections on Windows.
> Alternatively, if we're going to get in bed with the internals of
> Windows' fd_set implementation anyway, we could implement our own
> version of FD_SET that doesn't do the de-duplication.
Yes. See attached, which I cannot test.
--
Fabien.
Attachment | Content-Type | Size |
---|---|---|
pgbench-select-win-3.patch | text/x-diff | 1.1 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Geoghegan | 2020-06-05 19:43:13 | Re: Potential G2-item cycles under serializable isolation |
Previous Message | Tom Lane | 2020-06-05 18:10:52 | Re: pgbench bug / limitation |