Postgres Pro
Downloads
Home   >   mailing lists

RE: SIGTERM -> elog(FATAL) -> proc_exit() is probably a bad idea - Mailing list pgsql-hackers

From Hiroshi Inoue
Subject RE: SIGTERM -> elog(FATAL) -> proc_exit() is probably a bad idea
Date
Msg-id EKEJJICOHDIEMGPNIFIJEEMKDEAA.Inoue@tpf.co.jp
Whole thread Raw
In response to SIGTERM -> elog(FATAL) -> proc_exit() is probably a bad idea  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: SIGTERM -> elog(FATAL) -> proc_exit() is probably a bad idea
List pgsql-hackers
Tree view 
> -----Original Message-----
> From: Tom Lane
> 
> I have just finished trudging through a bunch of code and trying to make
> it secure against being interrupted by die() at arbitrary instants.

It seems that START/END_CRIT_SECTION() is called in both
existent and newly added places.
Isn't it appropriate to call a diffrent macro using a separate 
CriticalSectionCount variable in newly added places ?

Regards.
Hiroshi Inoue

pgsql-hackers by date:

Previous
From: Lamar Owen
Date:
Subject: RPMS for 7.1beta3 in progress.
Next
From: Oleg Bartunov
Date:
Subject: R-Tree implementation using GiST