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 430ce18, hence there is no need for a
backpatch.

Author: Yushi Ogiwara
Reviewed-by: Fujii Masao, Tom Lane, Bruce Momjian
Discussion: https://postgr.es/m/[email protected]

Author: michaelpq

src/interfaces/libpq/fe-connect.c

@@ -6825,7 +6825,9 @@ conninfo_uri_decode(const char *str, PQExpBuffer errorMessage)
 	/* Not at the end of the string yet?  Fail. */
 	if (*q != '\0')
 	{
-		libpq_append_error(errorMessage, "trailing data found: \"%s\"", str);
+		libpq_append_error(errorMessage,
+						   "unexpected spaces found in \"%s\", use percent-encoded spaces (%%20) instead",
+						   str);
 		free(buf);
 		return NULL;
 	}

src/interfaces/libpq/t/001_uri.pl

@@ -96,13 +96,13 @@
 		# Trailing data in parameter.
 		q{postgresql://host?  user user  =  uri  & port = 12345 12 },
 		q{},
-		q{libpq_uri_regress: trailing data found: "  user user  "},
+		q{libpq_uri_regress: unexpected spaces found in "  user user  ", use percent-encoded spaces (%20) instead},
 	],
 	[
 		# Trailing data in value.
 		q{postgresql://host?  user  =  uri-user  & port = 12345 12 },
 		q{},
-		q{libpq_uri_regress: trailing data found: " 12345 12 "},
+		q{libpq_uri_regress: unexpected spaces found in " 12345 12 ", use percent-encoded spaces (%20) instead},
 	],
 	[ q{postgresql://host?}, q{host='host' (inet)}, q{}, ],
 	[