aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gist/giststrat.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2009-03-02 21:19:23 +0000
committerTom Lane <tgl@sss.pgh.pa.us>2009-03-02 21:19:23 +0000
commit1f3832b5d2728e5d4333324dbbb1ecd4634ded14 (patch)
tree85863ddee8d0d3150cfb61a8d679c44e0d4e23ca /src/backend/access/gist/giststrat.c
parent5156266ab65d67b92493663435051a8bf36ae47d (diff)
downloadpostgresql-1f3832b5d2728e5d4333324dbbb1ecd4634ded14.tar.gz
postgresql-1f3832b5d2728e5d4333324dbbb1ecd4634ded14.zip
When we are in error recursion trouble, arrange to suppress translation and
encoding conversion of any elog/ereport message being sent to the frontend. This generalizes a patch that I put in last October, which suppressed translation of only specific messages known to be associated with recursive can't-translate-the-message behavior. As shown in bug #4680, we need a more general answer in order to have some hope of coping with broken encoding conversion setups. This approach seems a good deal less klugy anyway. Patch in all supported branches.
Diffstat (limited to 'src/backend/access/gist/giststrat.c')
0 files changed, 0 insertions, 0 deletions