From: | "Chad R(dot) Larson" <clarson(at)eldocomp(dot)com> |
---|---|
To: | <nickf(at)ontko(dot)com>, "pgsql-admin" <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: Leftover processes on shutdown - Debian+JDBC |
Date: | 2002-08-14 21:24:29 |
Message-ID: | 4.2.2.20020814142044.00a79bc0@ecint.ecinet.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin pgsql-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
From | Date | Subject | |
---|---|---|---|
Next Message | Nick Fankhauser | 2002-08-14 21:32:30 | Re: Leftover processes on shutdown - Debian+JDBC |
Previous Message | Nick Fankhauser | 2002-08-14 19:48:12 | Re: Leftover processes on shutdown - Debian+JDBC |
From | Date | Subject | |
---|---|---|---|
Next Message | Nick Fankhauser | 2002-08-14 21:32:30 | Re: Leftover processes on shutdown - Debian+JDBC |
Previous Message | Nick Fankhauser | 2002-08-14 19:48:12 | Re: Leftover processes on shutdown - Debian+JDBC |