FW: postmaster going down own its on

***********************
Your mail has been scanned by InterScan VirusWall.
***********-***********

the scenario in which the above took place was somewhat like this
we have a script to stop some of the processes running in the background.

this script was run, and all the processes got stopped

then another script will start these processes one after the other in background
that script was run, and postmaster also got started.

and then all of a sudden, it went down.

thanks for the suggestions, i ll also look into the log essages and look for
"received fast shutdown" message.

but in case the postmaster received a fast shutdown signal, when the above mentioned script (to stop all processes in background).

but again the script to start the processes including postmaster was run

and at that time, postmaster did start, then how come it suddently went down.

will provide u with more info on the same,

thanks,
regards
surabhi

-----Original Message-----
From: Tom Lane [mailto:tgl@sss.pgh.pa.us]
Sent: Fri 4/7/2006 8:51 PM
To: Douglas McNaught
Cc: Martijn van Oosterhout; Richard Huxton; surabhi.ahuja; pgsql-general@postgresql.org
Subject: Re: [GENERAL] postmaster going down own its on

***********************
Your mail has been scanned by InterScan VirusWall.
***********-***********


Douglas McNaught <doug@mcnaught.org> writes:
> Tom Lane <tgl@sss.pgh.pa.us> writes:
>> Could be.  The actual standard use of SIGTERM is to kill processes
>> belonging to your terminal process group when you log out.

> I thought that was SIGHUP?

Doh.  Not enough caffeine absorbed yet.

As penance, here's a comment that I think is actually correct: sending
SIGINT to the postmaster will make it turn around and send SIGTERM to
all the backends.  So there are two different explanations for the
backends giving the "administrator command" error: either some outside
force sent them SIGTERM directly, or some outside force sent the
postmaster SIGINT.  The SIGINT-the-postmaster theory is the more likely,
I suspect, and that again could be associated with having carelessly
left the postmaster attached to one's terminal.  In any case, the first
thing to do is look in the postmaster log and see if you see a message
about "received fast shutdown request", which would be proof one way or
the other.

                        regards, tom lane