]> git.ipfire.org Git - thirdparty/postgresql.git/commit
Use ereport not elog for some corrupt-HOT-chain reports.
authorTom Lane <tgl@sss.pgh.pa.us>
Thu, 1 Mar 2018 21:23:30 +0000 (16:23 -0500)
committerTom Lane <tgl@sss.pgh.pa.us>
Thu, 1 Mar 2018 21:23:49 +0000 (16:23 -0500)
commitfb1d72f409497a8e217f877184ff1e0056e1394e
tree9d38cdd044ff28ecdaba7611118069216fff37f2
parent491bbc36ea8f206dd0e03687b4d6a773be43a5f9
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
src/backend/catalog/index.c