aboutsummaryrefslogtreecommitdiff
path: root/src/backend/utils/adt/float.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2009-03-02 21:18:50 +0000
committerTom Lane <tgl@sss.pgh.pa.us>2009-03-02 21:18:50 +0000
commiteb828d9398b0cf383502cca2f1706496033b2ab6 (patch)
treedbb0d408e4af341b38a2582f0f3a5fd41a4d2123 /src/backend/utils/adt/float.c
parent327c5e37d7c87aded85d348a3236d71a6e2d34e7 (diff)
downloadpostgresql-eb828d9398b0cf383502cca2f1706496033b2ab6.tar.gz
postgresql-eb828d9398b0cf383502cca2f1706496033b2ab6.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/utils/adt/float.c')
0 files changed, 0 insertions, 0 deletions