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.
elog.c (r18.104.22.168 -> r22.214.171.124)
pgsql-committers by date
|Next:||From: User Mkz||Date: 2007-07-23 08:53:52|
|Subject: pgbouncer - pgbouncer: Fix sloppy english in the comments.|
|Previous:||From: Tom Lane||Date: 2007-07-21 22:12:32|
|Subject: pgsql: Fix elog.c to avoid infinite recursion (leading to backend crash) |