Re: Leftover processes on shutdown - Debian+JDBC

The tests I did were on a "quiet" system- I shut down Tomcat to ensure that
any old transactions were closed, then brought it back up and immediately
did the tests before any new transactions had started. (On a development
system, so no users could have snuck in.) Our application opens a group of
pooled persistent connections on startup, so there were about 4 connections
open, but they weren't doing anything.

Does -m fast actually close connections on your server?

-Nick

> -----Original Message-----
> From: Chad R. Larson [mailto:clarson(at)eldocomp(dot)com]
> Sent: Wednesday, August 14, 2002 4:24 PM
> To: nickf(at)ontko(dot)com; pgsql-admin
> Subject: Re: [ADMIN] Leftover processes on shutdown - Debian+JDBC
>
>
> At 12:48 PM 8/14/02 , Nick Fankhauser wrote:
> >Then I tried changing "smart" to "fast", and did the same two tests. The
> >results were exactly the same, so apparently "fast" mode does
> not forcibly
> >disconnect clients as the Docs state.
>
> As best I can tell, with "smart" the backend waits for the
> connection to go
> away, "fast" waits for the current transaction to complete and
> then exits,
> and with "immediate" the backend croaks right away (forcing a
> rollback and
> recovery on the next start up).
>
> If your Java servlet has requested some transaction that takes a =very=
> long time to run, you'd see what you see.
>
>
> -crl
> --
> Chad R. Larson (CRL22) chad(at)eldocomp(dot)com
> Eldorado Computing, Inc. 602-604-3100
> 5353 North 16th Street, Suite 400
> Phoenix, Arizona 85016-3228
>