]> git.ipfire.org Git - thirdparty/postgresql.git/commit
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)
commit987b0664fbab1e7b5e88484ed3b8b200d2a27cd1
tree43e88c5d8e4cb5ff32d260d3ca22fd842328f676
parent6d8afdee000f719c8d63ae383053803935e880d9
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