aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gist/gistvacuum.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2018-03-01 16:23:29 -0500
committerTom Lane <tgl@sss.pgh.pa.us>2018-03-01 16:23:45 -0500
commit8ecdc2ffe3da3a84d01e51c784ec3510157c893b (patch)
tree014760d0327b6539a7168939bb3ed66c5b6cc414 /src/backend/access/gist/gistvacuum.c
parent477ad05e165c15dc9241376f0fce9664063cff46 (diff)
downloadpostgresql-8ecdc2ffe3da3a84d01e51c784ec3510157c893b.tar.gz
postgresql-8ecdc2ffe3da3a84d01e51c784ec3510157c893b.zip
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
Diffstat (limited to 'src/backend/access/gist/gistvacuum.c')
0 files changed, 0 insertions, 0 deletions