Re: pgsql: aio: Infrastructure for io_method=worker - Mailing list pgsql-hackers

From Tom Lane
Subject Re: pgsql: aio: Infrastructure for io_method=worker
Date
Msg-id 593800.1742338428@sss.pgh.pa.us
Whole thread Raw
Responses Re: pgsql: aio: Infrastructure for io_method=worker
List pgsql-hackers
Andres Freund <andres@anarazel.de> 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.  Unsurprisingly, this broke OpenBSD/NetBSD
again:

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=sawshark&dt=2025-03-18%2016%3A20%3A05

It's probably time to just abandon the idea of being able to run with
only 60 semaphores.  I wonder though if we ought to revert 38da05346
and/or 6d0154196 in view of that.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Aidar Imamov
Date:
Subject: Re: Add pg_buffercache_evict_all() and pg_buffercache_mark_dirty[_all]() functions
Next
From: Andres Freund
Date:
Subject: Re: pgsql: aio: Infrastructure for io_method=worker