Re: Should io_method=worker remain the default?

From: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Jeff Davis <pgsql(at)j-davis(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Should io_method=worker remain the default?
Date: 2025-09-09 02:14:17
Message-ID: CA+hUKGLJJ5bs2JQzBPOo87UhMT2LhdN+5yJW2uNuz8RZ6p7+SA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Sep 9, 2025 at 1:59 PM Thomas Munro <thomas(dot)munro(at)gmail(dot)com> wrote:
> (3) even though it should
> win for Jeff's test case by skipping workers entirely if an initial
> RWF_NOWAIT attempt succeeds, you could presumably change some
> parameters and make it lose

... not to mention that with v19 patches even that effect should go
away when it automatically scales the worker pool to the perfect™
size.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Sami Imseih 2025-09-09 02:20:14 Re: PgStat_HashKey padding issue when passed by reference
Previous Message Thomas Munro 2025-09-09 01:59:20 Re: Should io_method=worker remain the default?