diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2009-03-02 21:19:05 +0000 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2009-03-02 21:19:05 +0000 |
| commit | 010953d904a1423ffb26017c5e9eda759bf143d7 (patch) | |
| tree | 06ccbfe81345dc0b810c6342a277d79def2dd157 /src/backend/access/gist/gistproc.c | |
| parent | 38a0507d0659af0f7f213bc7c739fd3792112d08 (diff) | |
| download | postgresql-010953d904a1423ffb26017c5e9eda759bf143d7.tar.gz postgresql-010953d904a1423ffb26017c5e9eda759bf143d7.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/gistproc.c')
0 files changed, 0 insertions, 0 deletions