| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
| Cc: | Richard Huxton <dev(at)archonet(dot)com>, Douglas McNaught <doug(at)mcnaught(dot)org>, "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 14:48:33 |
| Message-ID: | 11837.1144421313@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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 suppose the OP is bright enough to have noticed the connection between
closing the window and losing the postmaster, so it's probably not quite
that simple, but anyway something like this is what to look for.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Douglas McNaught | 2006-04-07 15:01:09 | Re: postmaster going down own its on |
| Previous Message | Mike Rylander | 2006-04-07 14:41:15 | Re: case insensitive match in unicode |