Re: pgbench: could not connect to server: Resource temporarily unavailable

From: Kevin McKibbin <kevinmckibbin123(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, pgsql-performance(at)lists(dot)postgresql(dot)org
Subject: Re: pgbench: could not connect to server: Resource temporarily unavailable
Date: 2022-08-22 21:14:23
Message-ID: CADc_NKh109RFvYEbmcGuAHDxixxJ0u3Qkso0Yry9s-H2ukY4aQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Thanks for your input everyone! I wanted to confirm that increasing the
somaxconn also fixed the issue for me.

Kevin

> $ cat /proc/sys/net/core/somaxconn
> 128
>
> by default, which is right about where the problem starts. After
>
> $ sudo sh -c 'echo 1000 >/proc/sys/net/core/somaxconn'
>
> *and restarting the PG server*, I can do a lot more threads without
> a problem. Evidently, the server's socket's listen queue length
> is fixed at creation and adjusting the kernel limit won't immediately
> change it.
>
>
>

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Thomas Munro 2022-08-23 02:42:13 Re: pgbench: could not connect to server: Resource temporarily unavailable
Previous Message Tom Lane 2022-08-22 16:57:43 Re: pgbench: could not connect to server: Resource temporarily unavailable