Horton

Re: PATCH: pgbench - option to build using ppoll() for larger connection counts

Tom Lane <tgl@sss.pgh.pa.us>

View thread View on postgr.es
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andres Freund <andres@anarazel.de>
Cc: "Rady, Doug" <radydoug@amazon.com>, Fabien COELHO <coelho@cri.ensmp.fr>, "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>, Robert Haas <robertmhaas@gmail.com>
Date: 2018-04-06T21:49:19Z
Lists: pgsql-hackers 
Andres Freund <andres@anarazel.de> writes:
> I'm still not particularly happy with this.

I'm a bit confused as to what the point is.  It seems unlikely that one
pgbench process can effectively drive enough backends for select's
limitations to really be an issue.

			regards, tom lane

Commits

  1. Use ppoll(2), if available, to wait for input in pgbench.

  2. Use pselect(2) not select(2), if available, to wait in postmaster's loop.