Herouth Maoz <herouth@xxxxxxxxxxxxx> writes: > So Iâ??m left with the question of what caused the shutdown on July 21st. Well, you had 2015-07-21 15:37:59 IDT LOG: received fast shutdown request There is exactly one place in the Postgres code that prints that message, and it is the postmaster's SIGINT handler. 2015-07-21 15:37:59 IDT LOG: aborting any active transactions This is just the postmaster noting that it's about to send SIGTERM signals to all its child processes ... 2015-07-21 15:37:59 IDT FATAL: terminating connection due to administrator command ... and here is a child acknowledging receipt of SIGTERM. This is all as-expected once the postmaster's received a shutdown signal. So something sent the postmaster a SIGINT, and it's hard to believe that the source wasn't external to the database. If your application is running on a different machine then it couldn't have been the application's fault. If you didn't issue "pg_ctl stop -m fast" then we can eliminate that. There has to have been some other software on the database server machine that sent the signal, and it had to have privileges to do so which means it was either running as the postgres O/S user or as root. One thing worth considering is the possibility that the postmaster had been started in such a way that it was still associated with a controlling terminal; then any control-C typed on that terminal would have resulted in a SIGINT. regards, tom lane -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
