| From: | Andreas Karlsson <andreas(at)proxel(dot)se> |
|---|---|
| To: | Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Possible typo in an error message |
| Date: | 2026-07-10 07:31:15 |
| Message-ID: | 3292adea-a80e-40d9-9696-69300ad4046f@proxel.se |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 7/10/26 06:52, Kyotaro Horiguchi wrote:
> While translating this message, I noticed the following error text:
>
> parse_jsontable.c:644:
>> errdetail("PATH name was %s not found in nested columns list.",
>
> Is this perhaps meant to be
>
> PATH name %s was not found in nested columns list.
>
> instead?
Agreed, or maybe:
"Path name %s not found in nested columns list."
From what I can see both forms are used in our error messages.
> Also, I wasn't quite sure whether the uppercase "PATH" in messages
> such as "PATH name" has any particular significance. For the
> translation, I ended up treating it as the ordinary word "path", since
> I couldn't tell whether it was intended to refer to the SQL keyword or
> just the general concept.
Agreed, it does not look like it is a keyword so it should not be
written in upper case.
> I found another occurrence of the similar wording:
>
> parse_jsontable.c:324:
>> errdetail("PATH name mismatch: expected %s but %s is given."
That looks like it should be "Path name" too.
--
Andreas Karlsson
Percona
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Etsuro Fujita | 2026-07-10 07:40:51 | Re: use of SPI by postgresImportForeignStatistics |
| Previous Message | Fujii Masao | 2026-07-10 07:13:56 | Fix pg_stat_progress_data_checksums counter initialization |