diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2022-08-23 10:14:45 -0400 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2022-08-23 10:15:06 -0400 |
| commit | 0f47457f1129fa21131465aba5663a14b2a09386 (patch) | |
| tree | 37d4d753337c23dd0124924e239ca2a3c566051e /src/backend/access/gist/gist.c | |
| parent | ba94dfd4c4f63cf8663f16e427bcc6fac35a4428 (diff) | |
| download | postgresql-0f47457f1129fa21131465aba5663a14b2a09386.tar.gz | |
Remove our artificial PG_SOMAXCONN limit on listen queue length.
I added this in commit 153f40067, out of paranoia about kernels
possibly rejecting very large listen backlog requests. However,
POSIX has said for decades that the kernel must silently reduce
any value it considers too large, and there's no evidence that
any current system doesn't obey that. Let's just drop this limit
and save some complication.
While we're here, compute the request as twice MaxConnections not
twice MaxBackends; the latter no longer means what it did in 2001.
Per discussion of a report from Kevin McKibbin.
Discussion: https://postgr.es/m/CADc_NKg2d+oZY9mg4DdQdoUcGzN2kOYXBu-3--RW_hEe0tUV=g@mail.gmail.com
Diffstat (limited to 'src/backend/access/gist/gist.c')
0 files changed, 0 insertions, 0 deletions