OSDN Git Service

Reduce PANIC to ERROR in several xlog routines that are used in both
authorTom Lane <tgl@sss.pgh.pa.us>
Fri, 15 Apr 2005 22:19:48 +0000 (22:19 +0000)
committerTom Lane <tgl@sss.pgh.pa.us>
Fri, 15 Apr 2005 22:19:48 +0000 (22:19 +0000)
commit5f0a974ea928b7ddd163210009f40843b982d658
tree2e912c55d8a2c1fd7e60d4af648a8353f5e74252
parent61b861421b0b849a0dffe36238b8e504624831c1
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.)
src/backend/access/transam/xlog.c