pgsql: Add "break"s to make it clearer what will happen in a nested swi

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Add "break"s to make it clearer what will happen in a nested swi
Date: 2017-03-12 20:01:47
Message-ID: E1cn9gZ-0007L1-8D@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Add "break"s to make it clearer what will happen in a nested switch.

This could only matter if the guessed_type variable had a value that wasn't
a member of the PasswordType enum; but just in case, let's be sure that
control falls out to reach the elog(ERROR) at the end of the function.
Per gripe from Coverity.

Branch
------
master

Details
-------
http://git.postgresql.org/pg/commitdiff/766f7fd613adbceaf1b40803793e10dc487f8596

Modified Files
--------------
src/backend/libpq/crypt.c | 2 ++
1 file changed, 2 insertions(+)

Browse pgsql-committers by date

  From Date Subject
Next Message David Rowley 2017-03-12 21:44:29 Re: pgsql: dblink: Replace some macros by static functions
Previous Message Andres Freund 2017-03-11 23:43:36 pgsql: Improve expression evaluation test coverage.