diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2009-03-02 21:19:14 +0000 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2009-03-02 21:19:14 +0000 |
| commit | 40df3efa763cd00c0ee4fe0cec3a650afb710e46 (patch) | |
| tree | d20f5d4cae09d075df9bb778e2ac400fa5706f3d /src/backend/utils/adt/formatting.c | |
| parent | 5f1f0db8727d8f0377f530ba1b05741891166a57 (diff) | |
| download | postgresql-40df3efa763cd00c0ee4fe0cec3a650afb710e46.tar.gz postgresql-40df3efa763cd00c0ee4fe0cec3a650afb710e46.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/formatting.c')
0 files changed, 0 insertions, 0 deletions