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

From: "Mikheev, Vadim" <vmikheev(at)SECTORBASE(dot)COM>
To: "'Tom Lane'" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgreSQL(dot)org
Subject: RE: SIGTERM -> elog(FATAL) -> proc_exit() is probably a bad idea
Date: 2001-01-12 22:09:05
Message-ID: 8F4C99C66D04D4118F580090272A7A234D3275@sectorbase1.sectorbase.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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

Vadim

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2001-01-12 22:09:50 Re: [HACKERS] problems with pg_geqo
Previous Message Bruce Momjian 2001-01-12 22:06:58 Re: CVS updates on committers list...