Re: Add missing error codes to PANIC/FATAL error reports in xlog.c and relcache.c

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: Nazir Bilal Yavuz <byavuz81(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, kksrcv001(at)gmail(dot)com, Andres Freund <andres(at)anarazel(dot)de>
Subject: Re: Add missing error codes to PANIC/FATAL error reports in xlog.c and relcache.c
Date: 2024-03-06 08:59:24
Message-ID: ADD37D21-E5BE-4B05-A21C-37870699F740@yesql.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On 26 Feb 2024, at 13:42, Nazir Bilal Yavuz <byavuz81(at)gmail(dot)com> wrote:

> All of your feedback is addressed in v2.

Nothing sticks out from reading through these patches, they seem quite ready to
me. Being able to filter and analyze on errorcodes is likely to be more
important going forward as more are running fleets of instances. I'm marking
these Ready for Committer, unless there are objections I think we should go
ahead with these. There are probably more errors in the system which could
benefit from the same treatment, but we need to start somewhere.

--
Daniel Gustafsson

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bertrand Drouvot 2024-03-06 09:05:59 Re: Missing LWLock protection in pgstat_reset_replslot()
Previous Message Kyotaro Horiguchi 2024-03-06 08:57:44 Re: Infinite loop in XLogPageRead() on standby