pgsql: Fix elog.c to avoid infinite recursion (leading to backend crash) - Mailing list pgsql-committers

From tgl@postgresql.org (Tom Lane)
Subject pgsql: Fix elog.c to avoid infinite recursion (leading to backend crash)
Date
Msg-id 20070721221204.CC6609FB25C@postgresql.org
Whole thread Raw
List 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.

Modified Files:
--------------
    pgsql/src/backend/utils/error:
        elog.c (r1.189 -> r1.190)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/error/elog.c.diff?r1=1.189&r2=1.190)

pgsql-committers by date:

Previous
From: tgl@postgresql.org (Tom Lane)
Date:
Subject: pgsql: Provide a bit more high-level documentation for the GEQO planner.
Next
From: tgl@postgresql.org (Tom Lane)
Date:
Subject: pgsql: Fix elog.c to avoid infinite recursion (leading to backend crash)