pgsql: Reduce PANIC to ERROR in several xlog routines that are used in - Mailing list pgsql-committers

From tgl@svr1.postgresql.org (Tom Lane)
Subject pgsql: Reduce PANIC to ERROR in several xlog routines that are used in
Date
Msg-id 20050415221948.31C4053653@svr1.postgresql.org
Whole thread Raw
List pgsql-committers
Log Message:
-----------
Reduce PANIC to ERROR in several xlog routines that are used in both
critical and noncritical contexts (an example of noncritical being
post-checkpoint removal of dead xlog segments).  In the critical cases
the CRIT_SECTION mechanism will cause ERROR to be promoted to PANIC
anyway, and in the noncritical cases we shouldn't let an error take
down the entire database.  Arguably there should be *no* explicit
PANIC errors in this module, only more START/END_CRIT_SECTION calls,
but I didn't go that far.  (Yet.)

Modified Files:
--------------
    pgsql/src/backend/access/transam:
        xlog.c (r1.185 -> r1.186)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/transam/xlog.c.diff?r1=1.185&r2=1.186)

pgsql-committers by date:

Previous
From: jwp@pgfoundry.org (User Jwp)
Date:
Subject: python - ex: Fix logic(again) to allow all any exception with .code =
Next
From: momjian@svr1.postgresql.org (Bruce Momjian)
Date:
Subject: pgsql: Fix comment typo.