Re: SIGNALNAME in "pg_ctl kill" - Mailing list pgsql-general

From Robert Treat
Subject Re: SIGNALNAME in "pg_ctl kill"
Date
Msg-id CABV9wwMgH9u3ow31Ew0wTLcDNDLMJH8veROV2Y0yG-+9vkK=+Q@mail.gmail.com
Whole thread Raw
In response to Re: SIGNALNAME in "pg_ctl kill"  (Mike Blackwell <mike.blackwell@rrd.com>)
List pgsql-general
If you are trying to kill one specific connection/backend, I'd
recommend using the pg_terminate_backend(pid_goes_here) function.

Robert Treat
conjecture: xzilla.net
consulting: omniti.com

On Wed, Nov 9, 2011 at 5:18 PM, Mike Blackwell <mike.blackwell@rrd.com> wrote:
> The manual section on the postmaster process has some info:
> http://www.postgresql.org/docs/current/static/app-postgres.html
>
> __________________________________________________________________________________
> Mike Blackwell | Technical Analyst, Distribution Services/Rollout Management
> | RR Donnelley
> 1750 Wallace Ave | St Charles, IL 60174-3401
> Office: 630.313.7818
> Mike.Blackwell@rrd.com
> http://www.rrdonnelley.com
>
>
>
> On Wed, Nov 9, 2011 at 16:02, Gauthier, Dave <dave.gauthier@intel.com>
> wrote:
>>
>> pg_ctl --help lists the various SIGNALNAME options to use with "pg_ctk
>> kill"...
>>
>>
>>
>> Allowed signal names for kill:
>>
>>   HUP INT QUIT ABRT TERM USR1 USR2
>>
>>
>>
>> I can't find a description of what each does.  I'd like to abort just the
>> procpid I enter, but using ABRT has a tendancy to kill lots of other stuff
>> too.
>>
>>
>>
>> Thanks for any insights !
>

pgsql-general by date:

Previous
From: Emanuel Calvo
Date:
Subject: Weird waste time when UNION ALL to an empty result set
Next
From: Andrew Sullivan
Date:
Subject: Re: SIGNALNAME in "pg_ctl kill"