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

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

On Mon, Aug 22, 2022 at 2:18 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Thomas Munro <thomas(dot)munro(at)gmail(dot)com> writes:
> > On Mon, Aug 22, 2022 at 12:20 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> >> Hmm. It'll be awhile till the 128 default disappears entirely
> >> though, especially if assorted BSDen use that too. Probably
> >> worth the trouble to document.
>
> > I could try to write a doc patch if you aren't already on it.
>
> I haven't done anything about it yet, but could do so tomorrow or so.

Cool. BTW small correction to something I said about FreeBSD: it'd be
better to document the new name kern.ipc.soacceptqueue (see listen(2)
HISTORY) even though the old name still works and matches OpenBSD and
macOS.

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Tom Lane 2022-08-22 02:55:13 Re: pgbench: could not connect to server: Resource temporarily unavailable
Previous Message Tom Lane 2022-08-22 02:18:13 Re: pgbench: could not connect to server: Resource temporarily unavailable