pgsql: Fix crash/valgrind error

From: Peter Eisentraut <peter(at)eisentraut(dot)org>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Fix crash/valgrind error
Date: 2025-04-04 12:46:20
Message-ID: E1u0gRA-002dHN-0l@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Fix crash/valgrind error

Fix for commit 9ef1851685b: We have to skip indexes where sortopfamily
is NULL. This takes the place of the previous btree check. Detected
by valgrind on the buildfarm.

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/ee1ae8b99f964ca1edc038dd558e541832164d52

Modified Files
--------------
src/backend/utils/adt/selfuncs.c | 4 ++++
1 file changed, 4 insertions(+)

Browse pgsql-committers by date

  From Date Subject
Next Message Alexander Korotkov 2025-04-04 13:17:00 pgsql: Convert 'x IN (VALUES ...)' to 'x = ANY ...' then appropriate
Previous Message Heikki Linnakangas 2025-04-04 12:18:21 pgsql: docs: Clarify that NULL arg to set_config() means reset to defau