aboutsummaryrefslogtreecommitdiff
path: root/src
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2018-08-24 10:51:10 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2018-08-24 10:51:10 -0400
commitb0c5da615ec45bcd24b97a1d55b1f489b9830a4b (patch)
tree6868b04f057f01372e6eb800b8e4f8505026b2dd /src
parentdb72302b0a846b0790ddc487c109d7c0880d4bcc (diff)
downloadpostgresql-b0c5da615ec45bcd24b97a1d55b1f489b9830a4b.tar.gz
postgresql-b0c5da615ec45bcd24b97a1d55b1f489b9830a4b.zip
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.
Diffstat (limited to 'src')
-rw-r--r--src/backend/libpq/auth.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/backend/libpq/auth.c b/src/backend/libpq/auth.c
index 68bb62d873c..85175655359 100644
--- a/src/backend/libpq/auth.c
+++ b/src/backend/libpq/auth.c
@@ -865,7 +865,7 @@ CheckSCRAMAuth(Port *port, char *shadow_pass, char **logdetail)
StringInfoData sasl_mechs;
int mtype;
StringInfoData buf;
- void *scram_opaq;
+ void *scram_opaq = NULL;
char *output = NULL;
int outputlen = 0;
char *input;