Re: Leftover processes on shutdown - Debian+JDBC
От | Robert M. Meyer |
---|---|
Тема | Re: Leftover processes on shutdown - Debian+JDBC |
Дата | |
Msg-id | 1029256582.28282.38.camel@skymaster обсуждение исходный текст |
Ответ на | Re: Leftover processes on shutdown - Debian+JDBC (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: Leftover processes on shutdown - Debian+JDBC
Hardware Tuning |
Список | pgsql-admin |
Hmmm... You're right. How much longer does a '-m fast' take. The reason I ask is because during a server shutdown, init doesn't wait around long after the script exits. The problem with not using the '-m' is that pg_ctl returns quickly but the DB may not be down, causing the system to pull the rug out from under it. Cheers! Bob On Tue, 2002-08-13 at 12:20, Tom Lane wrote: > "Robert M. Meyer" <rmeyer@installs.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 -- Robert M. Meyer Sr. Network Administrator DigiVision Satellite Services 14 Lafayette Sq, Ste 410 Buffalo, NY 14203-1904 (716)332-1451
В списке pgsql-admin по дате отправления: