pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Nathan Bossart <nathandbossart@gmail.com>
To: Andres Freund <andres@anarazel.de>
Cc: Jeff Davis <pgsql@j-davis.com>
Cc: pgsql-hackers@postgresql.org
Subject: Re: Should io_method=worker remain the default?
Date: Mon, 8 Sep 2025 15:14:01 -0500
Message-ID: <aL85CeasM51-0D1h@nathan> (raw)
In-Reply-To: <cmrpnnmbd4tajrg3lfnvzfo224siwyxzc6homaf2bvpmabiln5@jzfsvlsyoqtj>
References: <d68e2a4f8c356107e5167408ad80eaa2fac0f57d.camel@j-davis.com>
	<adywrhdn5zcfeldzug2pkzbdxizactr46goh4doiztvexrqomy@lgvl26gui63a>
	<a81f2f7ef34afc24a89c613671ea017e3651329c.camel@j-davis.com>
	<1b50102876dc9564049c985cff0ec1903cc8d502.camel@j-davis.com>
	<cmrpnnmbd4tajrg3lfnvzfo224siwyxzc6homaf2bvpmabiln5@jzfsvlsyoqtj>

On Mon, Sep 08, 2025 at 01:43:45PM -0400, Andres Freund wrote:
> 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.

I think we need to do something similar for numeric.c.

inline patch 1: src/backend/utils/adt/meson.build (+9/-1 lines) download inline-1.patchdiff --git a/src/backend/utils/adt/meson.build b/src/backend/utils/adt/meson.build index dac372c3bea..7d0688ddb87 100644 --- a/src/backend/utils/adt/meson.build +++ b/src/backend/utils/adt/meson.build @@ -1,5 +1,14 @@ # Copyright (c) 2022-2025, PostgreSQL Global Development Group +numeric_backend_lib = static_library('numeric_backend_lib', + 'numeric.c', + dependencies: backend_build_deps, + kwargs: internal_lib_args, + c_args: vectorize_cflags, +) + +backend_link_with += numeric_backend_lib + backend_sources += files( 'acl.c', 'amutils.c', @@ -61,7 +70,6 @@ backend_sources += files( 'network_gist.c', 'network_selfuncs.c', 'network_spgist.c', - 'numeric.c', 'numutils.c', 'oid.c', 'oracle_compat.c',
-- nathan

view thread (28+ messages)  latest in thread

Message-ID: <aL85CeasM51-0D1h@nathan>
Permalink:  ../aL85CeasM51-0D1h@nathan/
Also on:    postgresql.org/message-id/aL85CeasM51-0D1h@nathan

 ·  · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: nathandbossart@gmail.com, andres@anarazel.de, pgsql@j-davis.com
  Subject: Re: Should io_method=worker remain the default?
  In-Reply-To: <aL85CeasM51-0D1h@nathan>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox