Skip site navigation (1) Skip section navigation (2)

Peripheral Links

Header And Logo

PostgreSQL
| The world's most advanced open source database.

Site Navigation

Search for
  Advanced Search

Re: hard shutdown of system


  • From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
  • To: "surabhi.ahuja" <surabhi(dot)ahuja(at)iiitb(dot)ac(dot)in>
  • Cc: pgsql-general(at)postgresql(dot)org
  • Subject: Re: hard shutdown of system
  • Date: Mon, 17 Apr 2006 10:18:51 -0400
  • Message-id: <542(dot)1145283531(at)sss(dot)pgh(dot)pa(dot)us>

"surabhi.ahuja" <surabhi(dot)ahuja(at)iiitb(dot)ac(dot)in> writes:
> the user tries to do kill -9 -1 and log in again

The *first* thing you gotta do is retrain your user.  kill -9
is never the appropriate way to shut down the postmaster.

The script mods you describe seem to be oriented at forcing the
postmaster to restart when there are still live child processes
of the old postmaster.  That is a REALLY BAD IDEA.  It will lead
to unrecoverable corruption of your database.  The safety checks
that are in the postmaster are there to keep you from destroying
your database --- overriding them by removing the pid file is
not safe, recommended, or supported.

The last question is why your user wants to shut down the postmaster
so often?  There shouldn't be any need for that in ordinary scenarios.

			regards, tom lane



Home | Main Index | Thread Index

Privacy Policy | PostgreSQL Archives hosted by Command Prompt, Inc. | Designed by tinysofa
Copyright © 1996 – 2008 PostgreSQL Global Development Group