pgsql: Reduce PANIC to ERROR in several xlog routines that are used in

From: tgl(at)svr1(dot)postgresql(dot)org (Tom Lane)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Reduce PANIC to ERROR in several xlog routines that are used in
Date: 2005-04-15 22:19:48
Message-ID: 20050415221948.31C4053653@svr1.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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)

Browse pgsql-committers by date

  From Date Subject
Next Message Bruce Momjian 2005-04-15 22:49:45 pgsql: Fix comment typo.
Previous Message User Jwp 2005-04-15 21:45:45 python - ex: Fix logic(again) to allow all any exception with .code =