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

From: tgl(at)postgresql(dot)org (Tom Lane)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Fix elog.c to avoid infinite recursion (leading to backend crash)
Date: 2007-07-21 22:12:11
Message-ID: 20070721221211.8B0999FB25C@postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Log Message:
-----------
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.

Tags:
----
REL8_2_STABLE

Modified Files:
--------------
pgsql/src/backend/utils/error:
elog.c (r1.178.2.3 -> r1.178.2.4)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/error/elog.c.diff?r1=1.178.2.3&r2=1.178.2.4)

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2007-07-21 22:12:17 pgsql: Fix elog.c to avoid infinite recursion (leading to backend crash)
Previous Message Tom Lane 2007-07-21 22:12:04 pgsql: Fix elog.c to avoid infinite recursion (leading to backend crash)