Re: Clarify where the severity level is defined

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: Kuwamura Masaki <kuwamura(at)db(dot)is(dot)i(dot)nagoya-u(dot)ac(dot)jp>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Clarify where the severity level is defined
Date: 2023-09-28 13:39:41
Message-ID: BA69CD8E-630E-4209-911D-6E7FFDBBA8F8@yesql.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On 25 Sep 2023, at 08:37, Daniel Gustafsson <daniel(at)yesql(dot)se> wrote:
>
>> On 25 Sep 2023, at 08:22, Kuwamura Masaki <kuwamura(at)db(dot)is(dot)i(dot)nagoya-u(dot)ac(dot)jp> wrote:
>
>> Recently I read the document about ereport()[1].
>> Then, I felt that there is little information about severity level.
>> So I guess it can be kind to clarify where severity level is defined(see attached patch please).
>
> That makes sense, we already point to other related files on that page so this
> is line with that.

Committed, with some minor wordsmithing. Thanks!

--
Daniel Gustafsson

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2023-09-28 13:41:06 Re: Is it worth adding Assert(false) for unknown paths in print_path()?
Previous Message Drouvot, Bertrand 2023-09-28 13:01:42 Re: Synchronizing slots from primary to standby