From: Tom Lane <tgl@sss.pgh.pa.us>
To: Nagy László Zsolt <gandalf@shopzeus.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Could not shut down DB
Date: Mon, 30 May 2016 12:43:11 -0400
Message-ID: <12880.1464626591@sss.pgh.pa.us> (raw)
In-Reply-To: <a08117a1-054f-9fa4-9fc5-469c69bfcda2@shopzeus.com>
References: <a08117a1-054f-9fa4-9fc5-469c69bfcda2@shopzeus.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>
=?UTF-8?Q?Nagy_L=c3=a1szl=c3=b3_Zsolt?= <gandalf@shopzeus.com> writes:
> I could stop it with:
> pg_ctl stop -i i
> but before that:
> May 30 07:21:00 appserver postgres[65202]: [5-1] FATAL: the database
> system is shutting down
> May 30 07:21:00 appserver postgres[65203]: [5-1] FATAL: the database
> system is shutting down
> May 30 07:21:00 appserver postgres[65206]: [5-1] FATAL: the database
> system is shutting down
> It happened in the weekend, and the server log does not contain anything
> except these "FATAL: shutting down" messages, so I'm not able to tell
> when is started. Any idea what could possible cause this error?
Well, the default-until-recently "smart" shutdown mode would wait for
all existing sessions to finish, while not letting any new ones in.
That sure looks like what you have here.
regards, tom lane
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, gandalf@shopzeus.com
Subject: Re: Could not shut down DB
In-Reply-To: <12880.1464626591@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox