pgsql: Suppress maybe-uninitialized warning.

From: Masahiko Sawada <msawada(at)postgresql(dot)org>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Suppress maybe-uninitialized warning.
Date: 2025-08-05 22:32:05
Message-ID: E1ujQCT-000wPP-0h@gemulon.postgresql.org
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Suppress maybe-uninitialized warning.

Following commit e035863c9a0, building with -O0 began triggering
warnings about potentially uninitialized 'workbuf' usage. While
theoretically the initialization isn't necessary since VARDATA()
doesn't access the contents of the pointed-to object, this commit
explicitly initializes the workbuf variable to suppress the warning.

Buildfarm members adder and flaviventris have shown the warning.

Reviewed-by: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Discussion: https://postgr.es/m/CAD21AoCOZxfqnNgfM5yVKJZYnOq5m2Q96fBGy1fovEqQ9V4OZA@mail.gmail.com

Branch
------
master

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

Modified Files
--------------
src/backend/storage/large_object/inv_api.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Fujii Masao 2025-08-06 07:49:50 pgsql: doc: Recommend ANALYZE after ALTER TABLE ... SET EXPRESSION AS.
Previous Message Tom Lane 2025-08-05 20:51:29 pgsql: Fix incorrect return value in brin_minmax_multi_distance_numeric