Request a Demo
Home   >   mailing lists

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

From [email protected] (Tom Lane)
Subject pgsql: Fix elog.c to avoid infinite recursion (leading to backend crash)
Date
Msg-id [email protected]
Whole thread Raw
List pgsql-committers
Tree view 
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:
----
REL7_3_STABLE

Modified Files:
--------------
    pgsql/src/backend/utils/error:
        elog.c (r1.104.2.1 -> r1.104.2.2)

(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/error/elog.c.diff?r1=1.104.2.1&r2=1.104.2.2)

pgsql-committers by date:

Previous
From: [email protected] (Tom Lane)
Date:
Subject: pgsql: Fix elog.c to avoid infinite recursion (leading to backend crash)
Next
From: [email protected] (User Mkz)
Date:
Subject: pgbouncer - pgbouncer: Fix sloppy english in the comments.