Re: Should io_method=worker remain the default?

From: Andres Freund <andres(at)anarazel(dot)de>
To: Jeff Davis <pgsql(at)j-davis(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Should io_method=worker remain the default?
Date: 2025-09-08 17:43:45
Message-ID: cmrpnnmbd4tajrg3lfnvzfo224siwyxzc6homaf2bvpmabiln5@jzfsvlsyoqtj
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

On 2025-09-05 16:07:09 -0700, Jeff Davis wrote:
> On Fri, 2025-09-05 at 13:25 -0700, Jeff Davis wrote:
> > As an aside, I'm building with meson using -Dc_args="-msse4.2 -Wtype-
> > limits -Werror=missing-braces". But I notice that the meson build
> > doesn't seem to use -funroll-loops or -ftree-vectorize when building
> > checksums.c. Is that intentional? If not, perhaps slower checksum
> > calculations explain my results.

Yes, that's an oversight.

> Attached a patch. I'm not sure if it's the right way to do things, but
> the resulting compiler command seems right to me.
>
> It doesn't affect my tests in this thread much, but it seems best to be
> consistent with autoconf.

Yes, we should do this - the patch looks good to me.

Greetings,

Andres Freund

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2025-09-08 17:46:41 Re: [PG19-3 PATCH] Don't ignore passfile
Previous Message Masahiko Sawada 2025-09-08 17:43:32 Re: POC: enable logical decoding when wal_level = 'replica' without a server restart