pgsql: Fix last remaining uninitialized memory warnings

From: Peter Eisentraut <peter(at)eisentraut(dot)org>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Fix last remaining uninitialized memory warnings
Date: 2023-08-09 08:05:52
Message-ID: E1qTeCV-001A28-Tv@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Fix last remaining uninitialized memory warnings

gcc (version 13) fails to properly analyze the code due to the loop
stop condition including `l != NULL`. Let's just help it out.

Author: Tristan Partin <tristan(at)neon(dot)tech>
Discussion: https://www.postgresql.org/message-id/flat/CT6HJ3U8068R(dot)3A8SJMV02D9BC(at)gonk

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/4a8fef0d733965c1a1836022f8a42ab1e83a721f

Modified Files
--------------
src/bin/pgbench/pgbench.c | 2 +-
src/bin/pgbench/pgbench.h | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Alvaro Herrera 2023-08-09 09:11:55 Re: pgsql: Ignore BRIN indexes when checking for HOT udpates
Previous Message Michael Paquier 2023-08-08 23:57:09 pgsql: Fix pg_dumpall with in-place tablespaces