Tom-
I just spent some time trying to reproduce the behavior I saw yesterday, and
I can't do it... In fact -m fast is doing exactly what it is supposed to.
Apologies for the false alarm!
So going back to my original question about the leftover processes- Doing a
pg_ctl stop -m fast solves the problem nicely, and Oliver said he is going
to change the script in the Debian package accordingly.
-Nick
> -----Original Message-----
> From: pgsql-admin-owner@postgresql.org
> [mailto:pgsql-admin-owner@postgresql.org]On Behalf Of Tom Lane
> Sent: Wednesday, August 14, 2002 5:16 PM
> To: nickf@ontko.com
> Cc: Chad R. Larson; pgsql-admin
> Subject: Re: [ADMIN] Leftover processes on shutdown - Debian+JDBC
>
>
> "Nick Fankhauser" <nickf@ontko.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
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo@postgresql.org so that your
> message can get through to the mailing list cleanly
>
