is it also possible that someone was doing an operation on the database for instance inserting manyr rows
and suddenly a command to stop the postmaster arrived?
thanks,
regards
Surabhi
From: Tom Lane [mailto:tgl@sss.pgh.pa.us]
Sent: Tue 1/24/2006 8:22 PM
To: Richard Huxton
Cc: surabhi.ahuja; pgsql-general@postgresql.org
Subject: Re: [GENERAL] FATAL: terminating connection due to administrator command
***********************
Your mail has been scanned by iiitb VirusWall.
***********-***********
Richard Huxton <dev@archonet.com> writes:
> surabhi.ahuja wrote:
>> so does this mean that someone is trying to stop postmaster by
>> sending it a kill signal?
> Someone or something. It can be Linux's out-of-memory facility picking
> processes to kill. Google "oom killer" for discussion.
No, because the OOM killer invariably uses "kill -9". "Fast shutdown"
means that something sent the postmaster a SIGINT.
If you launch the postmaster manually and are not careful to make it
dissociate from your terminal, then typing ^C at some unrelated program
later would be enough to make this happen ...
>> 1. many times i have seen two instances of postmaster running. how
>> does that happen and how to prevent it from happening?
> Shouldn't (unless you have two installations of course).
Perhaps he's not understanding the difference between the postmaster and
its child processes? I don't believe he's actually got two postmasters
running (unless maybe in separate directories with separate ports, which
is hardly likely to be a setup one would create by accident). There are
*very* extensive safety interlocks in place to prevent that.
regards, tom lane
