| From: | PG Bug reporting form <noreply(at)postgresql(dot)org> |
|---|---|
| To: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Cc: | evsi(at)amazon(dot)com |
| Subject: | BUG #19368: f54af9f does not create the correct macro for autotools build |
| Date: | 2025-12-31 00:25:09 |
| Message-ID: | 19368-016d79a7f3a1c599@postgresql.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
The following bug has been logged on the website:
Bug reference: 19368
Logged by: Evan Si
Email address: evsi(at)amazon(dot)com
PostgreSQL version: 18.1
Operating system: Amazon Linux 2, Amazon Linux 2023
Description:
https://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=f54af9f2679d
The commit f54af9f2679d added a macro HAVE_LIBURING_QUEUE_INIT_MEM that is
checked to see if slowdown from memory mappings can be avoided when using
io_uring.
This HAVE_LIBURING_QUEUE_INIT_MEM is set by Meson build after checking
liburing.
However, the autotools build seems to set a different macro,
HAVE_IO_URING_QUEUE_INIT_MEM, which is never used.
This means when the server is built with autotools, the slowdown when using
io_uring can never be avoided.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2025-12-31 15:59:32 | Re: BUG #19368: f54af9f does not create the correct macro for autotools build |
| Previous Message | Amit Kapila | 2025-12-30 06:55:37 | Re: BUG #19360: Bug Report: Logical Replication initial sync fails with "conflict=update_origin_differs" PG12 toPG18 |