Re: Should io_method=worker remain the default? - Mailing list pgsql-hackers

From Andres Freund
Subject Re: Should io_method=worker remain the default?
Date
Msg-id cmrpnnmbd4tajrg3lfnvzfo224siwyxzc6homaf2bvpmabiln5@jzfsvlsyoqtj
Whole thread Raw
In response to Re: Should io_method=worker remain the default?  (Jeff Davis <pgsql@j-davis.com>)
Responses Re: Should io_method=worker remain the default?
List 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



pgsql-hackers by date:

Previous
From: Masahiko Sawada
Date:
Subject: Re: POC: enable logical decoding when wal_level = 'replica' without a server restart
Next
From: Tom Lane
Date:
Subject: Re: [PG19-3 PATCH] Don't ignore passfile