| From: | Douglas McNaught <doug(at)mcnaught(dot)org> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Martijn van Oosterhout <kleptog(at)svana(dot)org>, Richard Huxton <dev(at)archonet(dot)com>, "surabhi(dot)ahuja" <surabhi(dot)ahuja(at)iiitb(dot)ac(dot)in>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: postmaster going down own its on |
| Date: | 2006-04-07 15:01:09 |
| Message-ID: | 873bgp2zwq.fsf@suzuka.mcnaught.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
> Martijn van Oosterhout <kleptog(at)svana(dot)org> writes:
>> On Fri, Apr 07, 2006 at 03:03:09PM +0100, Richard Huxton wrote:
>>> What would be sending SIGTERM to a backend?
>
>> The only other thing I've ever heard of is some systems do a sigterm
>> when you pass a quota limit?
>
> Could be. The actual standard use of SIGTERM is to kill processes
> belonging to your terminal process group when you log out. So, for
> example, manually starting the postmaster from a terminal window and
> then closing that window could cause this to happen.
I thought that was SIGHUP?
-Doug
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-04-07 15:21:26 | Re: postmaster going down own its on |
| Previous Message | Tom Lane | 2006-04-07 14:48:33 | Re: postmaster going down own its on |