pgsql: Get rid of another unconstify through API changes

From: Peter Eisentraut <peter(at)eisentraut(dot)org>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Get rid of another unconstify through API changes
Date: 2019-02-14 20:04:18
Message-ID: E1guNF4-0002ab-Kb@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Get rid of another unconstify through API changes

This also makes the code in read_client_first_message() more similar
to read_client_final_message().

Reported-by: Mark Dilger <hornschnorter(at)gmail(dot)com>
Discussion: https://www.postgresql.org/message-id/flat/53a28052-f9f3-1808-fed9-460fd43035ab%402ndquadrant.com

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/86eea78694ce0d95e74cc82cc29c096d66a9accd

Modified Files
--------------
src/backend/libpq/auth-scram.c | 56 +++++++++++++++++++++---------------------
src/backend/libpq/auth.c | 2 +-
src/include/libpq/scram.h | 2 +-
3 files changed, 30 insertions(+), 30 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2019-02-15 00:37:36 pgsql: Simplify the planner's new representation of indexable clauses a
Previous Message Peter Eisentraut 2019-02-14 16:03:10 pgsql: Resolve one unconstify use