From: Tom Lane <tgl@sss.pgh.pa.us>
To: =?UTF-8?Q?Nagy_L=c3=a1szl=c3=b3_Zsolt?= <gandalf@shopzeus.com>
cc: pgsql-admin@postgresql.org
Subject: Re: Could not shut down DB
In-reply-to: <a08117a1-054f-9fa4-9fc5-469c69bfcda2@shopzeus.com>
References: <a08117a1-054f-9fa4-9fc5-469c69bfcda2@shopzeus.com>
Comments: In-reply-to =?UTF-8?Q?Nagy_L=c3=a1szl=c3=b3_Zsolt?=
 <gandalf@shopzeus.com>
	message dated "Mon, 30 May 2016 07:26:43 +0200"
Date: Mon, 30 May 2016 12:43:11 -0400
Message-ID: <12880.1464626591@sss.pgh.pa.us>
Precedence: bulk
Sender: pgsql-admin-owner@postgresql.org

=?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