Re: Leftover processes on shutdown - Debian+JDBC

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Robert M(dot) Meyer" <rmeyer(at)installs(dot)com>
Cc: nickf(at)ontko(dot)com, 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 16:20:29
Message-ID: 26784.1029255629@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin pgsql-jdbc

"Robert M. Meyer" <rmeyer(at)installs(dot)com> writes:
> 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

A much safer choice would be "-m fast".

The default ("-m smart") doesn't shut down the server until all clients
voluntarily disconnect. If you have tomcat holding persistent
connections open then that's not what you want.

"-m fast" forcibly disconnects clients and then does a clean database
shutdown. This is generally what you want if you have
persistent-connection clients.

"-m immediate" is the equivalent of the big red EMERGENCY STOP button
found in places like power plant control rooms. If you are in the habit
of hitting that as a routine measure, you need to have your operator's
permit revoked.

regards, tom lane

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Nick Fankhauser 2002-08-13 16:20:48 Re: Leftover processes on shutdown - Debian+JDBC
Previous Message Thomas O'Connell 2002-08-13 16:14:39 Re: performance tuning: shared_buffers, sort_mem; swap

Browse pgsql-jdbc by date

  From Date Subject
Next Message Nick Fankhauser 2002-08-13 16:20:48 Re: Leftover processes on shutdown - Debian+JDBC
Previous Message Robert M. Meyer 2002-08-13 16:04:47 Re: Leftover processes on shutdown - Debian+JDBC