From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | nickf(at)ontko(dot)com |
Cc: | "Chad R(dot) Larson" <clarson(at)eldocomp(dot)com>, "pgsql-admin" <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: Leftover processes on shutdown - Debian+JDBC |
Date: | 2002-08-14 22:16:28 |
Message-ID: | 16782.1029363388@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin pgsql-jdbc |
"Nick Fankhauser" <nickf(at)ontko(dot)com> writes:
> Does -m fast actually close connections on your server?
It works as advertised for me: not only will it cut connections, but it
will abort queries-in-progress. For instance, I did this:
regression=# begin;
BEGIN
regression=# select * from tenk1 a, tenk1 b, tenk1 c;
-- the above would return 100billion rows if given the chance, so
-- after a second or two I issued "pg_ctl stop -m fast" in another
-- window, and promptly got:
FATAL: This connection has been terminated by the administrator.
server closed the connection unexpectedly
This probably means the server terminated abnormally
before or while processing the request.
The connection to the server was lost. Attempting reset: Failed.
!#
Successful shutdown was reported by pg_ctl a couple seconds later,
as expected.
Not sure what's going wrong for you --- are you certain you did the test
correctly? Any possibility you ran the wrong script, shut down the
wrong server, etc?
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | David Hsu | 2002-08-15 03:55:11 | pg_restore does not restore/recreate indices |
Previous Message | Kris Deugau | 2002-08-14 22:10:40 | DB Access Restrictions |
From | Date | Subject | |
---|---|---|---|
Next Message | Larry Riedel | 2002-08-14 22:34:14 | 7.3 Cursors/ResultSets/CallableStatements |
Previous Message | Kris Deugau | 2002-08-14 22:10:40 | DB Access Restrictions |