| From: | Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com> |
|---|---|
| To: | Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com> |
| Cc: | Álvaro Herrera <alvherre(at)kurilemu(dot)de>, Pg Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Zsolt Parragi <zsolt(dot)parragi(at)percona(dot)com> |
| Subject: | Re: unclear OAuth error message |
| Date: | 2026-03-27 17:03:11 |
| Message-ID: | CAOYmi+kxTcDPaoGWVPTgEv_JkBN13dxvpbs+V8df3NBH07x_nA@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Mar 23, 2026 at 10:18 PM Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com> wrote:
> I also have a small comment on the doc change. The documentation already mentions the memory requirements for error_detail, so I wonder if it also makes sense to mention its style. Since it is emitted as a DETAIL message, I think it should probably follow the usual style rules for detail messages, i.e., start with a capital letter and end with a period.
Sure, I think it makes sense to add a quick link to our style guide as
part of the "best practices" section.
Thanks,
--Jacob
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sami Imseih | 2026-03-27 17:09:04 | Re: Refactor query normalization into core query jumbling |
| Previous Message | Jacob Champion | 2026-03-27 17:01:59 | Re: unclear OAuth error message |