Re: Should io_method=worker remain the default?

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

On Mon, Sep 8, 2025 at 2:39 PM Thomas Munro <thomas(dot)munro(at)gmail(dot)com> wrote:
> You might also be interested in the phenomenon discussed in the index
> prefetching thread, where concurrent reads of the *same* block from
> different backs currently force a wait, which can be avoided with a
> patch he posted. In that thread it was happening due to index scans

Sorry, bad edit: I meant a patch that Andres posted.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Chao Li 2025-09-08 02:49:44 Re: Allow logical replication in the same cluster
Previous Message Thomas Munro 2025-09-08 02:39:35 Re: Should io_method=worker remain the default?