Re: Quote-less file names in error messages

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Quote-less file names in error messages
Date: 2025-04-04 07:40:01
Message-ID: 577B11BA-1E2C-41C4-A198-74AA34C18D82@yesql.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On 4 Apr 2025, at 05:03, Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com> wrote:
>
> Hello,
>
> The recent commit 2da74d8d640 added the following new messages:
>
> + libpq_append_conn_error(conn, "could not open ssl keylog file %s: %s",
> + libpq_append_conn_error(conn, "could not write to ssl keylog file %s: %s
>
> However, I believe our convention is to quote file names in such messages.

Thanks for the report, I'll get it fixed.

> - A WARNING message in `fd.c` seems worth fixing (0002).

Thi is an elog() and not an error intended to be common for users, so I'm not
sure it's worth the churn really as it's been there since 2012. Changing it
might introduce conflicts in backpatching for little gain.

> - Two DEBUG2 messages in `xlog.c` seem less important to fix (0003).
>
> - I don't think it's worth bothering with those in developer tools (0004).

Agreed.

--
Daniel Gustafsson

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Alexander Korotkov 2025-04-04 07:55:32 Re: Changing the state of data checksums in a running cluster
Previous Message Peter Eisentraut 2025-04-04 07:38:29 Re: Thread-safe nl_langinfo() and localeconv()