| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Shutdown term |
| Date: | 2001-03-13 20:31:36 |
| Message-ID: | 200103132031.PAA28015@candle.pha.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> > The connection was terminated.
> > And make the postmaster print out
> > The system is shutting down.
> > before it sends out the SIGTERM's.
>
> Unfortunately the postmaster is in no position to send any message to
> the individual clients.
>
> Maybe we should forget the idea of having a single message to cover
> both cases, and instead provide some flag in shared memory that the
> postmaster can set before it sends out SIGTERMs. Then the backends
> would actually know why they got a SIGTERM and could emit
> more-appropriate messages.
Seems like overkill to me. We could have the postmaster use SIGQUIT for
db shutdown and leave SIGKILL for admin shutdown of individual backends.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2001-03-13 20:34:26 | Re: Shutdown term |
| Previous Message | Tom Lane | 2001-03-13 20:06:49 | Re: Shutdown term |