From: Tom Lane Date: Thu, 1 May 2025 21:36:47 +0000 (-0400) Subject: Add missing newlines to PQescapeInternal() messages pre-v16. X-Git-Tag: REL_13_21~8 X-Git-Url: http://git.postgresql.org/gitweb/?a=commitdiff_plain;h=06a2c598e10b0f698b57a6c0be7ebafd19a5d6f1;p=postgresql.git Add missing newlines to PQescapeInternal() messages pre-v16. While back-patching 9f45e6a91, I neglected that the convention in pre-v16 libpq was to include a trailing newline in error message strings (since then, we add those separately). Add them now. Reported-by: Peter Eisentraut Discussion: https://postgr.es/m/a9c837ad-d507-4607-94e4-c5743a8f49e0@eisentraut.org Backpatch-through: 13-15 --- diff --git a/src/interfaces/libpq/fe-exec.c b/src/interfaces/libpq/fe-exec.c index a2afd6de65a..8630da31a28 100644 --- a/src/interfaces/libpq/fe-exec.c +++ b/src/interfaces/libpq/fe-exec.c @@ -3410,10 +3410,10 @@ PQescapeStringInternal(PGconn *conn, { if (remaining < charlen) printfPQExpBuffer(&conn->errorMessage, - libpq_gettext("incomplete multibyte character")); + libpq_gettext("incomplete multibyte character\n")); else printfPQExpBuffer(&conn->errorMessage, - libpq_gettext("invalid multibyte character")); + libpq_gettext("invalid multibyte character\n")); /* Issue a complaint only once per string */ already_complained = true; }