pgsql: Fix incorrect parameter name in prototype

From: Daniel Gustafsson <dgustafsson(at)postgresql(dot)org>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Fix incorrect parameter name in prototype
Date: 2024-04-19 08:05:04
Message-ID: E1rxjF1-002oBM-KV@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Fix incorrect parameter name in prototype

The function declaration for select_next_encryption_method use the
variable name have_valid_connection, so fix the prototype in the
header to match that.

Reported-by: Alexander Lakhin <exclusion(at)gmail(dot)com>
Discussion: https://postgr.es/m/3F577953-A29E-4722-98AD-2DA9EFF2CBB8@yesql.se

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/9c58bf1507bee00b8cda837a232401fec21e6873

Modified Files
--------------
src/interfaces/libpq/fe-connect.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Dean Rasheed 2024-04-19 08:41:34 pgsql: Use macro NUM_MERGE_MATCH_KINDS instead of '3' in MERGE code.
Previous Message Tom Lane 2024-04-19 05:08:18 pgsql: Fix MSVC recipe for ecpg regression tests, redux.