public inbox for [email protected]  

help / color / mirror / Atom feed

From: Andres Freund <[email protected]>
To: Tom Lane <[email protected]>
Cc: [email protected]
Subject: Re: pgsql: aio: Infrastructure for io_method=worker
Date: Tue, 18 Mar 2025 19:07:53 -0400
Message-ID: <27fwadt6whe5ufqyrgbrnu3ppfiocaljtt3fufedn6sclvjqll@kotindcvgtoy> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>

Hi,

On 2025-03-18 18:53:48 -0400, Tom Lane wrote:
> Andres Freund <[email protected]> writes:
> > To allow the number of IO workers to be increased without a restart, we need
> > to reserve PGPROC entries for the workers unconditionally. This has been
> > judged to be worth the cost. If it turns out to be problematic, we can
> > introduce a PGC_POSTMASTER GUC to control the maximum number.
> 
> So I see this patch added 32 PGPROCs and hence 32 semaphores to the
> system's requirements.

Yea - I brought that suspicion up a few times in the thread and in the
resulting discussion it wasn't deemed worth introducing a PGC_POSTMASTER guc
to control the max.


> It's probably time to just abandon the idea of being able to run with
> only 60 semaphores.

Agreed. It's an absurdly outdated OS default configuration. Realistically one
can't run postgres even in a toy scenario without changing it. So the value of
being able to test postgres with the default OS settings doesn't seem that
high. If it were on a very commonly used platform I would think differently,
but net/openbsd ain't that.


> I wonder though if we ought to revert 38da05346 and/or 6d0154196 in view of
> that.

38da05346 doesn't seem to have much value if it doesn't help us run the tests
by default - but it also doesn't really hurt. So, shrug, I guess.

6d0154196 - a higher autovacuum_worker_slots increases resource usage more
than IO workers do, because autovac workers are included in computations like
lock space. But 16 isn't that much either way...

Greetings,

Andres Freund

view thread (5+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected]
  Subject: Re: pgsql: aio: Infrastructure for io_method=worker
  In-Reply-To: <27fwadt6whe5ufqyrgbrnu3ppfiocaljtt3fufedn6sclvjqll@kotindcvgtoy>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox