Re: Should io_method=worker remain the default?
Nathan Bossart <nathandbossart@gmail.com>
From: Nathan Bossart <nathandbossart@gmail.com>
To: Jeff Davis <pgsql@j-davis.com>
Cc: Andres Freund <andres@anarazel.de>, pgsql-hackers@postgresql.org
Date: 2025-09-10T16:25:15Z
Lists: pgsql-hackers
On Tue, Sep 09, 2025 at 04:11:49PM -0700, Jeff Davis wrote: > On Tue, 2025-09-09 at 10:39 -0500, Nathan Bossart wrote: >> My first instinct was to consider this for back-patching, but I see that >> you didn't back-patch commit 9af672b. Is there any technical reason we >> shouldn't be back-patching these types of meson build script changes? > > I think you are right, I can't see any harm in backporting it, and > arguably it's a bug: it would be annoying to compare performance across > different versions with different build flags. > > I backported through 16. Cool. I committed/back-patched the numeric.c fix to v16 as well. -- nathan
Commits
-
meson: Build numeric.c with -ftree-vectorize.
- 9016fa7e3bcd 19 (unreleased) landed
- 87ea6e9b66b6 18.0 landed
- 509c779293f2 16.11 landed
- 15f9eeef624f 17.7 landed
-
meson: build checksums with extra optimization flags.
- 2de24ca6ca51 16.11 landed
- e25453a3631f 17.7 landed
- a7024398b80a 18.0 landed
- 9af672bcb245 19 (unreleased) landed