Fix elog.c to avoid infinite recursion (leading to backend crash) when
authorTom Lane <tgl@sss.pgh.pa.us>
Sat, 21 Jul 2007 22:12:17 +0000 (22:12 +0000)
committerTom Lane <tgl@sss.pgh.pa.us>
Sat, 21 Jul 2007 22:12:17 +0000 (22:12 +0000)
commitc44001f7752881962005e21ff8a047a934025a96
tree66c8f2706394b5966d78249ec55b7b5adc0f8848
parent56b97a42a08ef686f0ac514c26e1f37da08b53d0
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.
src/backend/utils/error/elog.c