Use ereport not elog for some corrupt-HOT-chain reports.

Tom Lane <tgl@sss.pgh.pa.us>

Commit: 8ecdc2ffe3da3a84d01e51c784ec3510157c893b
Author: Tom Lane <tgl@sss.pgh.pa.us>
Date: 2018-03-01T21:23:45Z
Releases: 11.0
Use ereport not elog for some corrupt-HOT-chain reports.

These errors have been seen in the field in corrupted-data situations.
It seems worthwhile to report them with ERRCODE_DATA_CORRUPTED, rather
than the generic ERRCODE_INTERNAL_ERROR, for the benefit of log monitoring
and tools like amcheck.  However, use errmsg_internal so that the text
strings still aren't translated; it seems unlikely to be worth
translators' time to do so.

Back-patch to 9.3, like the predecessor commit d70cf811f that introduced
these elog calls originally (replacing Asserts).

Peter Geoghegan

Discussion: https://postgr.es/m/CAH2-Wzmn4-Pg-UGFwyuyK-wiTih9j32pwg_7T9iwqXpAUZr=Mg@mail.gmail.com

Files

PathChange+/−
src/backend/catalog/index.c modified +12 −7

Discussion