| From: | "Chad R(dot) Larson" <clarson(at)eldocomp(dot)com> |
|---|---|
| To: | "Robert M(dot) Meyer" <rmeyer(at)installs(dot)com>, nickf(at)ontko(dot)com |
| Cc: | pgsql-jdbc <pgsql-jdbc(at)postgresql(dot)org>, pgsql-admin <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: Leftover processes on shutdown - Debian+JDBC |
| Date: | 2002-08-13 17:44:32 |
| Message-ID: | 4.2.2.20020813103901.00abb840@ecint.ecinet.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin pgsql-jdbc |
At 08:25 AM 8/13/02 , Robert M. Meyer wrote:
>I had the same problem. I rewrote my shutdown script to call 'pg_ctl -m
>immediate'. So far, I haven't seen any damage because of it and we always
>restart tomcat at some point in the middle of the night, anyway.
We're running PostgreSQL as a backend to a J2SE server (with Macromedia
JRun instead of Tomcat). When we converted our Sun Enterprise servers into
a cluster (Veritas VCS) we had similar problems. We were using the "fast"
option on a shutdown, but switchover in the cluster would hang until we
changed the "fast" to "immediate". We'd prefer "fast", but it does not
seem to work exactly as documented.
Solaris 2.6, PostgreSQL 7.1.2, VCS 1.1.
-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 | Tom Lane | 2002-08-13 17:53:14 | Re: Leftover processes on shutdown - Debian+JDBC |
| Previous Message | Andrew Sullivan | 2002-08-13 17:06:23 | Re: tuning postgresql |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2002-08-13 17:53:14 | Re: Leftover processes on shutdown - Debian+JDBC |
| Previous Message | Oliver Elphick | 2002-08-13 16:56:18 | Re: Leftover processes on shutdown - Debian+JDBC |