Skip site navigation (1) Skip section navigation (2)

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:39
Message-ID: 20070721221239.155AF9FB279@postgresql.org (view raw or flat)
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:
----
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

Next:From: User MkzDate: 2007-07-23 08:53:52
Subject: pgbouncer - pgbouncer: Fix sloppy english in the comments.
Previous:From: Tom LaneDate: 2007-07-21 22:12:32
Subject: pgsql: Fix elog.c to avoid infinite recursion (leading to backend crash)

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group