From: | Doug McNaught <doug(at)wireboard(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Backends dying due to memory exhaustion--I'm stonkered |
Date: | 2001-01-27 04:41:07 |
Message-ID: | m3r91pr4ik.fsf@belphigor.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:
> Doug McNaught <doug(at)wireboard(dot)com> writes:
> > From what I've seen so far, all the backends (other than the one that
> > actually crashes) seem to survive the SIGTERM I send to the
> > postmaster. How do I tell which one is which? The command line?
>
> SIGTERM to the postmaster commands polite shutdown, ie, don't accept
> new connections but allow existing clients to finish out their sessions.
> So unless your clients are short-lived I wouldn't expect SIGTERM'ing
> the postmaster to do much.
>
> If you want to force things to happen then you should send SIGINT to
> the postmaster, which in turn will SIGTERM its backends, which in
> theory will abort their transactions and shut down.
OK, this makes sense. I must have missed it in the manual. SIGINT it
is.
Waiting for the next crash with anticipation...
-Doug
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2001-01-27 04:45:58 | Re: This script will crash the connection |
Previous Message | Franck Martin | 2001-01-27 04:33:37 | ISO SQL Geographic Objects |