Re: Automatically sizing the IO worker pool

Thomas Munro <thomas.munro@gmail.com>

From: Thomas Munro <thomas.munro@gmail.com>

To: Andres Freund <andres@anarazel.de>

Cc: Dmitry Dolgov <9erthalion6@gmail.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>

Date: 2026-04-08T02:24:57Z

Lists: pgsql-hackers

On Wed, Apr 8, 2026 at 2:09 PM Thomas Munro <thomas.munro@gmail.com> wrote:
> > Seems like there should be two fields. One saying "notify postmaster again"
> > and one "postmaster start a worker".  The former would only be cleared by
> > postmaster after the timeout.
>
> Good idea.  V7 has two tweaks:
>
> * separate grow and grow_signal_sent flags, as you suggested
> * it also applies the io_worker_launch_delay to cancelled grow requests

Oh, but that logic should of course be moved below the "time in the
past" check.  Will do...

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

aio: Adjust I/O worker pool automatically.
- d1c01b79d4ae 19 (unreleased) landed
Convert lwlock.c to use the new shmem allocation functions
- a006bc7b1699 19 (unreleased) cited
aio: Simplify pgaio_worker_submit().
- fc44f106657a 19 (unreleased) landed
Conditional locking in pgaio_worker_submit_internal
- 29a0fb215779 19 (unreleased) cited
aio: Remove obsolete IO worker ID references.
- b4c19da93a08 18.0 landed
- 177c1f059338 19 (unreleased) landed
aio: Regularize IO worker internal naming.
- b2afb0676337 18.0 landed
- 01d618bcd782 19 (unreleased) landed