Re: pgbench bug / limitation

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: pgbench bug / limitation
Дата
Msg-id 7221.1590687090@sss.pgh.pa.us
обсуждение исходный текст
Ответ на pgbench bug / limitation  ("Jawarilal, Manish" <Manish.Jawarilal@dell.com>)
Ответы RE: pgbench bug / limitation
Список pgsql-bugs
"Jawarilal, Manish" <Manish.Jawarilal@dell.com> writes:
> OS: Windows 10
> C:\Program Files\PostgreSQL\12\bin>pgbench.exe -c 120 -r -T 3600 -h <DBServerName> -p 9432 -U DBUser testdb
> too many client connections for select()

Yeah ... pgbench can support fairly large connection counts on platforms
that have ppoll(), but Windows does not.  Without ppoll() we fall back
to select() which may not allow more than 100 or so.

Having said that ... it looks like pgbench thinks it can override
Windows' default setting:

#ifdef WIN32
#define FD_SETSIZE 1024            /* must set before winsock2.h is included */
#endif

and some googling confirms that indeed that should work.  How did you
build or come by this copy of pgbench?

            regards, tom lane



В списке pgsql-bugs по дате отправления:

Предыдущее
От: "Jawarilal, Manish"
Дата:
Сообщение: pgbench bug / limitation
Следующее
От: Joe Conway
Дата:
Сообщение: Re: BUG #16466: Valgrind detects an invalid read in dblink_open()with a cursor inside a transaction