|From:||Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>|
|To:||Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com>|
|Cc:||Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>, "Rady, Doug" <radydoug(at)amazon(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, Robert Haas <robertmhaas(at)gmail(dot)com>|
|Subject:||Re: PATCH: pgbench - option to build using ppoll() for larger connection counts|
|Views:||Raw Message | Whole Thread | Download mbox | Resend email|
>> The author hasn't replied, but the attached seems to have cured the
>> bitrot so that it at least applies. Let's see what the cfbot makes of
>> it and then possibly fix any Windows issues.
The patch was not applying cleanly anymore for me, so here is a rebase of
your latest version.
Morever, ISTM that Tom's "why?" question has been answered: there are very
large systems out there with many processors, which are tested against
many connections, exceeding select limit.
I have turned back this patch to ready.
|Next Message||Andrew Dunstan||2018-09-15 14:26:17||Re: Defaulting to jit=on/off for v11|
|Previous Message||Alvaro Herrera||2018-09-15 13:15:28||Re: move PartitionDispatchData definition to execPartition.c|