diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2009-03-02 21:18:43 +0000 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2009-03-02 21:18:43 +0000 |
| commit | fd9e2accefb1a1763c58c19e07e1e18d0424d459 (patch) | |
| tree | 61eaec70d4c7b4f52a55e748a5ab049dae2a685d /src/backend/executor/nodeLimit.c | |
| parent | 32032d42b51bf673bdc17b2248a6a32b4de30676 (diff) | |
| download | postgresql-fd9e2accefb1a1763c58c19e07e1e18d0424d459.tar.gz postgresql-fd9e2accefb1a1763c58c19e07e1e18d0424d459.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/executor/nodeLimit.c')
0 files changed, 0 insertions, 0 deletions