| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Tatsuo Ishii <ishii(at)sraoss(dot)co(dot)jp> |
| Cc: | pgsql-docs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: No mention about somaxconn |
| Date: | 2020-03-06 18:06:57 |
| Message-ID: | 20200306180657.fybtyz72lyxjn4kr@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
Hi,
On 2020-03-03 10:48:56 +0900, Tatsuo Ishii wrote:
> Currently there's no mention about net.core.somaxconn parameter needs
> to be adjusted if max_connections is large and UNIX domain socket is
> used for connection. Since the default for the kernel parameter is
> small (typically 128), it is easy to hit the limitation and you will
> get errors something like:
>
> could not connect to server: Resource temporarily unavailable
>
> I don't know if this should be applied to other OS as well though.
Yea, that'd be good. Care to suggest a patch?
Greetings,
Andres Freund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Doc comments form | 2020-03-09 15:20:10 | invalid parser name |
| Previous Message | PG Doc comments form | 2020-03-06 07:08:01 | reassign owned requirement of locks |