Re: unclear OAuth error message

From: Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com>
To: Jacob Champion <jacob(dot)champion(at)enterprisedb(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-24 05:18:17
Message-ID: 021A4CE7-63EF-446D-88DC-58B789D119DA@gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On Mar 24, 2026, at 05:21, Zsolt Parragi <zsolt(dot)parragi(at)percona(dot)com> wrote:
>
> This is definitely a nice improvement, I only have two minor questions:
>
> - errmsg("internal error in OAuth validator module"));
> + errmsg("internal error in OAuth validator module"),
> + ret->error_detail ? errdetail_log("%s", ret->error_detail) : 0);
> +
>
> Isn't including the detail for both the warning and the fatal error
> still overly verbose?
>

I have the same feeling. If the detail has already been printed together with the WARNING, then maybe there is no longer much need to pass it out through logdetail.

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.

Best regards,
--
Chao Li (Evan)
HighGo Software Co., Ltd.
https://www.highgo.com/

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Chao Li 2026-03-24 05:32:00 Re: pg_stat_replication.*_lag sometimes shows NULL during active replication
Previous Message zengman 2026-03-24 04:13:20 Re:rewriteGraphTable: Fix missing RTEs in FROM clause by setting inFromCl=true