On Tue, Feb 24, 2026 at 5:15 PM Andrew Dunstan <andrew@dunslane.net> wrote:
>
>
> On 2026-02-24 Tu 5:05 AM, Jakub Wartak wrote:
> > On Tue, Feb 24, 2026 at 9:40 AM Chao Li <li.evan.chao@gmail.com> wrote:
> > [..]
> >
> >> There is guidance in the documentation regarding error message style:
https://www.postgresql.org/docs/current/error-style-guide.html
> >> ```
> >> Detail and hint messages: Use complete sentences, and end each with a period. Capitalize the first word of
sentences.Put two spaces after the period if another sentence follows (for English text; might be inappropriate in
otherlanguages).
> >> ```
> >>
> >> I also noticed that some existing DETAIL and HINT messages do not fully follow this guideline. But I believe new
codeshould adhere to the documented style as much as possible. In particular, DETAIL and HINT messages should begin
witha capital letter and follow the complete-sentence convention.
> > Hi, v2 attached, WIP, the only known remaining issue to me is that
> > windows might fail to compile as it probably doesn't have concept of
> > uid_t... I'm wondering what to do there.
>
>
> I don't think it will arise, as Windows doesn't have the siginfo stuff,
> AFAIK.
>
Hi Andrew. Ok, so V3 is attached with just one change: uid_t/pid_t
changed to uint32 to make win32 happy.
Perhaps one question is whether this should be toggleable with GUC or not.
-J.
