| From: | Heikki Linnakangas <heikki(dot)linnakangas(at)iki(dot)fi> |
|---|---|
| To: | pgsql-committers(at)lists(dot)postgresql(dot)org |
| Subject: | pgsql: Silence unused-but-set-variable warnings with MEMORY_CONTEXT_CHE |
| Date: | 2026-11-18 14:25:13 |
| Message-ID: | E1xTgb2-00000000FTf-3EGR@gemulon.postgresql.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
Silence unused-but-set-variable warnings with MEMORY_CONTEXT_CHECKING
These variables were only used with assertions enabled. If you
compiled with assertions disabled and MEMORY_CONTEXT_CHECKING enabled,
the compiler would warn about that (-Wunused-but-set-variable).
USE_VALGRIND implies MEMORY_CONTEXT_CHECKING, so USE_VALGRIND without
assertions was another way to see it.
Author: Michael Paquier <michael(at)paquier(dot)xyz>
Discussion: https://www.postgresql.org/message-id/ajZD8TCSIYPJgCNJ@paquier.xyz
Branch
------
master
Details
-------
https://git.postgresql.org/pg/commitdiff/0cf2d43d326d78e039a984e53724b5c9d2439e99
Modified Files
--------------
src/backend/utils/mmgr/aset.c | 2 +-
src/backend/utils/mmgr/bump.c | 2 +-
src/backend/utils/mmgr/generation.c | 2 +-
src/backend/utils/mmgr/slab.c | 2 +-
4 files changed, 4 insertions(+), 4 deletions(-)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2026-11-18 15:14:35 | pgsql: Don't create a shell type for a function returning SETOF |
| Previous Message | Alexander Korotkov | 2026-11-18 14:23:32 | pgsql: Don't make WAIT FOR LSN depend on WAL written after a page bound |