Hi all, in elderly versions, where pg_terminate_backend is missing, you'd issue a kill -15 <pid> from the command line.
Bèrto On 27 July 2012 09:33, Chris Angelico <ros...@gmail.com> wrote: > On Fri, Jul 27, 2012 at 6:27 PM, Mark Morgan Lloyd > <markmll.pgsql-gene...@telemetry.co.uk> wrote: >> Assuming a *nix server: if a monitoring program determines that an >> established connection appears to be trying to so something inappropriate, >> what's the best way of terminating that session rapidly? > > select pg_terminate_backend(procpid) from pg_stat_activity where ..... > > The main difficulty is recognizing which PID to terminate, though. > There's a good lot of information available in pg_stat_activity; > logins, application names, and connection IP addresses are handy here. > But ultimately, it's just pg_terminate_backend. > > ChrisA > > -- > Sent via pgsql-general mailing list (pgsql-general@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-general -- ============================== If Pac-Man had affected us as kids, we'd all be running around in a darkened room munching pills and listening to repetitive music. -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
