Fix elog.c to avoid infinite recursion (leading to backend crash) when

Tom Lane <tgl@sss.pgh.pa.us>

Commit: 681690f4e374d88877ea2f4de1baa04f780abd8e
Author: Tom Lane <tgl@sss.pgh.pa.us>
Date: 2007-07-21T22:12:38Z
Releases: 7.3.20
Fix elog.c to avoid infinite recursion (leading to backend crash) when
log_min_error_statement is active and there is some problem in logging the
current query string; for example, that it's too long to include in the log
message without running out of memory.  This problem has existed since the
log_min_error_statement feature was introduced.  No doubt the reason it
wasn't detected long ago is that 8.2 is the first release that defaults
log_min_error_statement to less than PANIC level.
Per report from Bill Moran.

Files

PathChange+/−
src/backend/utils/error/elog.c modified +11 −6