pgsql: libpq: Improve error message when parsing URI parameters and key - Mailing list pgsql-committers

From Michael Paquier
Subject pgsql: libpq: Improve error message when parsing URI parameters and key
Date
Msg-id E1tDFqw-002V6V-HX@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
libpq: Improve error message when parsing URI parameters and keywords

The error message showing up when parameters or keywords include too
many whitespaces was "trailing data found", which was confusing because
there was no hint about what was actually wrong.

Issue introduced in 430ce189fc45, hence there is no need for a
backpatch.

Author: Yushi Ogiwara
Reviewed-by: Fujii Masao, Tom Lane, Bruce Momjian
Discussion: https://postgr.es/m/645bd22a53c4da8a1bc7e1e52d9d3b52@oss.nttdata.com

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/a3699daea2026de324ed7cc7115c36d3499010d3

Modified Files
--------------
src/interfaces/libpq/fe-connect.c | 4 +++-
src/interfaces/libpq/t/001_uri.pl | 4 ++--
2 files changed, 5 insertions(+), 3 deletions(-)


pgsql-committers by date:

Previous
From: Bruce Momjian
Date:
Subject: pgsql: doc: clarify pg_dump --no-comments meaning as SQL comments
Next
From: Fujii Masao
Date:
Subject: pgsql: Improve error message for database object stats manipulation fun