Re: Add missing error codes to PANIC/FATAL error reports in xlogrecovery - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Add missing error codes to PANIC/FATAL error reports in xlogrecovery
Date
Msg-id 515167.1701378175@sss.pgh.pa.us
Whole thread Raw
In response to Re: Add missing error codes to PANIC/FATAL error reports in xlogrecovery  (Andres Freund <andres@anarazel.de>)
Responses Re: Add missing error codes to PANIC/FATAL error reports in xlogrecovery
List pgsql-hackers
Andres Freund <andres@anarazel.de> writes:
> Wondering if we should add a ERRCODE_CLUSTER_CORRUPTED for cases like this. We
> have ERRCODE_DATA_CORRUPTED and ERRCODE_INDEX_CORRUPTED, which make
> ERRCODE_DATA_CORRUPTED feel a bit too specific in this kind of situation?

Maybe.  We didn't officially define DATA_CORRUPTED as referring to
table data, but given the existence of INDEX_CORRUPTED maybe we
should treat it as that.  In any case ...

> Hm, this one arguably is not corruption, but we still cannot
> continue. ERRCODE_OBJECT_NOT_IN_PREREQUISITE_STATE or maybe a new error code?

... I don't really like turning a whole bunch of error cases into
the same error code without some closer analysis.  I think you
are right that these need a bit more case-by-case thought.

            regards, tom lane



pgsql-hackers by date:

Previous
From: "Tristan Partin"
Date:
Subject: Re: meson: Stop using deprecated way getting path of files
Next
From: Andres Freund
Date:
Subject: Re: Add missing error codes to PANIC/FATAL error reports in xlogrecovery