From: Tom Lane <tgl@sss.pgh.pa.us>
To: pgsql-committers@lists.postgresql.org
Subject: pgsql: Suppress uninitialized-variable warning in new SCRAM code.
Date: Fri, 24 Aug 2018 14:51:39 +0000
Message-ID: <E1ftDR5-00066s-QO@gemulon.postgresql.org> (raw)
Suppress uninitialized-variable warning in new SCRAM code.
While we generally don't sweat too much about "may be used uninitialized"
warnings from older compilers, I noticed that there's a fair number of
buildfarm animals that are producing such a warning *only* for this
variable. So it seems worth silencing.
Branch
------
REL_11_STABLE
Details
-------
https://git.postgresql.org/pg/commitdiff/7ed1db3f4625c4cb873a21c380913433820d50ce
Modified Files
--------------
src/backend/libpq/auth.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-committers@postgresql.org
Cc: tgl@sss.pgh.pa.us, pgsql-committers@lists.postgresql.org
Subject: Re: pgsql: Suppress uninitialized-variable warning in new SCRAM code.
In-Reply-To: <E1ftDR5-00066s-QO@gemulon.postgresql.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox