RE: SIGTERM -> elog(FATAL) -> proc_exit() is probably a bad idea

From: "Hiroshi Inoue" <Inoue(at)tpf(dot)co(dot)jp>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: <pgsql-hackers(at)postgreSQL(dot)org>
Subject: RE: SIGTERM -> elog(FATAL) -> proc_exit() is probably a bad idea
Date: 2001-01-14 13:01:01
Message-ID: EKEJJICOHDIEMGPNIFIJEEMKDEAA.Inoue@tpf.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> -----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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Oleg Bartunov 2001-01-14 15:41:10 R-Tree implementation using GiST
Previous Message Horst Herb 2001-01-14 10:39:40 Re: CRCs