diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2009-03-02 21:18:57 +0000 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2009-03-02 21:18:57 +0000 |
| commit | 78206b3bdd38c6974a622d144a9a7adf984ea7f0 (patch) | |
| tree | 9f2320b06217bfed092781b7ac3fa32c1f004394 /src/backend/access/gist/gistscan.c | |
| parent | 8fcdac99876df0bd04b8dd48fc37d8a286231033 (diff) | |
| download | postgresql-78206b3bdd38c6974a622d144a9a7adf984ea7f0.tar.gz postgresql-78206b3bdd38c6974a622d144a9a7adf984ea7f0.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/gistscan.c')
0 files changed, 0 insertions, 0 deletions