"Ed L." <pgsql@bluepolka.net> writes:
> On Monday February 23 2004 8:43, Sean Shanny wrote:
>> *LOG: received smart shutdown request *
>> *FATAL: the database system is shutting down
>> FATAL: the database system is shutting down
>> LOG: server process (PID 4691) was terminated by signal 9
>> LOG: terminating any other active server processes
>> LOG: statistics collector process (PID 361) was terminated by signal 9
> Looks like it got a SIGTERM, which is what you might get if someone shutdown
> OSX (osx pls gurus correct me).
Uh, no, signal 9 is SIGKILL not SIGTERM. I'm not aware of any automatic
mechanism in OS X that would issue SIGKILL against a Postgres backend.
Certainly Postgres itself would not. Some Linux kernels issue SIGKILL
to get out of out-of-memory situations, but I believe OS X to be better
behaved than that.
My private opinion is that Sean is mistaken and that the above trace
shows someone manually (and not very competently) shutting down the
database. First they tried a SIGTERM against the postmaster (or
equivalently "pg_ctl stop") and after getting tired of waiting for
the clients to shut down, they did SIGKILL against the backends.
It's too bad we have no timestamps in this log, as the intervals
between the above-recorded entries would be very revealing.
regards, tom lane
