re: pgbench stopped supporting large number of client connections on Windows

From: Ranier Vilela <ranier(dot)vf(at)gmail(dot)com>
To: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Cc: m(dot)polyakova(at)postgrespro(dot)ru
Subject: re: pgbench stopped supporting large number of client connections on Windows
Date: 2020-11-06 20:54:13
Message-ID: CAEudQAqP16wL-dea5p0EG-gvcjNx38XoAgWDa53=pioX=EtsGw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi Marina,
Nice catch.

>rc/bin/pgbench/pgbench.c, the function add_socket_to_set:
>if (fd < 0 || fd >= FD_SETSIZE)
>{
>/*
>* Doing a hard exit here is a bit grotty, but it doesn't seem worth
>* complicating the API to make it less grotty.
>*/
>pg_log_fatal("too many client connections for select()");
>exit(1);
>}

It seems to me that the limit is hardcode in,
src/backend/port/win32/socket.c

FD_SETSIZE * 2

that would be 2048?

regards,

Ranier Vilela

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Sergei Kornilov 2020-11-06 21:36:33 Re: Allow some recovery parameters to be changed with reload
Previous Message Jacob Champion 2020-11-06 20:37:48 Re: Support for NSS as a libpq TLS backend