Re: Add pg_stat_recovery system view

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Xuneng Zhou <xunengzhou(at)gmail(dot)com>, yangyz <1197620467(at)qq(dot)com>, pgsql-hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Add pg_stat_recovery system view
Date: 2026-03-09 06:06:20
Message-ID: aa5jXJLBHazYvd5m@paquier.xyz
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Mar 09, 2026 at 01:20:45PM +0800, Chao Li wrote:
>> [1] https://www.postgresql.org/docs/devel/error-message-reporting.html
>
> Would it make sense to mention this distinction in the header
> comments for ereport and elog in the code? For these logging APIs, I
> think developers are often more likely to read the code comments
> than the documentation.

As of the link already mentioned:
"Therefore, elog should be used only for internal errors .."
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Shreeya Sharma 2026-03-09 06:11:45 Re: POC: PLpgSQL FOREACH IN JSON ARRAY
Previous Message Shreeya Sharma 2026-03-09 06:03:27 Re: POC: PLpgSQL FOREACH IN JSON ARRAY