| From: | Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com> |
|---|---|
| To: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
| Cc: | Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: A few message wording/formatting cleanup patches |
| Date: | 2026-05-28 17:23:24 |
| Message-ID: | CAOYmi+mYWn2h=T-8WWH54iLmBxihEpH62=ARKxja1w4HFLkQZA@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, May 28, 2026 at 10:19 AM Daniel Gustafsson <daniel(at)yesql(dot)se> wrote:
> > On 28 May 2026, at 05:16, Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com> wrote:
> >> libpq_append_conn_error(conn,
> >> "server did not report the unsupported `_pq_.test_protocol_negotiation` parameter in its protocol negotiation message");
> >
> > but that doesn't seem to match our usual style. Nearby messages use
> > double quotes instead.
>
> Agreed. Shouldn't it also be adding the parameter as a %s to further match our style?
>
> - libpq_append_conn_error(conn, "server did not report the unsupported `_pq_.test_protocol_negotiation` parameter in its protocol negotiation message");
> + libpq_append_conn_error(conn, "server did not report the unsupported \"%s\" parameter in its protocol negotiation message", "_pq_.test_protocol_negotiation");
+1, will fix.
Thanks!
--Jacob
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jacob Champion | 2026-05-28 17:29:50 | Re: Make memory checking / sanitizing infrastructure better |
| Previous Message | Daniel Gustafsson | 2026-05-28 17:19:19 | Re: A few message wording/formatting cleanup patches |