Andres Freund b67b2cd702 Make stack depth check work with asan's use-after-return ... With address sanitizer's stack-use-after-return check, stack variables are moved to heap allocations, to allow to detect references to the memory at a later time. That broke our stack-depth check, which is why we had to disable detect_stack_use_after_return in CI. Luckily __builtin_frame_address() works correctly, even under asan, so use that. We started using __builtin_frame_address() with de447bb8e6, however as of that commit we just used it for the stack base address, not for the value to compare to the base address. Now we use it for both. When building without __builtin_frame_address() support, we continue to use stack variables for the stack depth determination. Reviewed-by: Tom Lane <tgl@sss.pgh.pa.us> Discussion: https://postgr.es/m/2kk4z4odvuyrg7qlwjd7ft4eron4cle4btb33v4qatgsdkayir@gj6e62rgsel4 Backpatch-through: 14		2026-05-28 11:34:14 -04:00
..
cmdtag.c	Update copyright for 2021	2021-01-02 13:06:25 -05:00
dest.c	Remove server and libpq support for old FE/BE protocol version 2.	2021-03-04 10:45:55 +02:00
fastpath.c	Message style improvements	2021-06-28 08:36:44 +02:00
Makefile	Represent command completion tags as structs	2020-03-02 18:19:51 -03:00
postgres.c	Make stack depth check work with asan's use-after-return	2026-05-28 11:34:14 -04:00
pquery.c	Remove assertion from PortalRunMulti	2025-07-17 17:40:22 +02:00
utility.c	Check for CREATE privilege on the schema in CREATE STATISTICS.	2025-11-10 09:00:00 -06:00