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

From: "Hiroshi Inoue" <Inoue(at)tpf(dot)co(dot)jp>
To: "Mikheev, Vadim" <vmikheev(at)SECTORBASE(dot)COM>, "'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-12 23:59:34
Message-ID: EKEJJICOHDIEMGPNIFIJEELGDEAA.Inoue@tpf.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> -----Original Message-----
> From: Mikheev, Vadim
>
> > I think we'd be lots better off to abandon the notion that we can exit
> > directly from the SIGTERM interrupt handler, and instead treat SIGTERM
> > the same way we treat QueryCancel: set a flag that is inspected at
> > specific places where we know we are in a good state.
> >
> > Comments?
>
> This will be much cleaner.
>

Hmm, CancelQuery isn't so urgent an operation currently.
For example, VACUUM checks QueryCancel flag only
once per table.

Regards.
Hiroshi Inoue

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2001-01-13 00:01:53 Re: SIGTERM -> elog(FATAL) -> proc_exit() is probably a bad idea
Previous Message Nathan Myers 2001-01-12 23:48:30 Re: CRCs