Received: from malur.postgresql.org ([2a02:16a8:dc51::56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1g6yE9-00079W-Jy for pgsql-pkg-debian@arkaria.postgresql.org; Mon, 01 Oct 2018 13:27:09 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1g6yE8-0000d9-4n for pgsql-pkg-debian@arkaria.postgresql.org; Mon, 01 Oct 2018 13:27:08 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1g6yE7-0000d2-Sr for pgsql-pkg-debian@lists.postgresql.org; Mon, 01 Oct 2018 13:27:08 +0000 Received: from feynman.df7cb.de ([195.49.152.168]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1g6yE4-00043r-Jr for pgsql-pkg-debian@postgresql.org; Mon, 01 Oct 2018 13:27:06 +0000 Received: from msg.df7cb.de (unknown [IPv6:2003:5b:203b:100:7627:eaff:fe52:8e03]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by feynman.df7cb.de (Postfix) with ESMTPSA id 42P33T0V1Mz3F07; Mon, 1 Oct 2018 15:27:01 +0200 (CEST) Date: Mon, 1 Oct 2018 15:27:00 +0200 From: Christoph Berg To: Giuseppe Sacco Cc: PostgreSQL in Debian Subject: Re: Problem in starting postgresql on a probably slow machine: pg_ctlcluster ignores pg_ctl timeout Message-ID: <20181001132700.GC15085@msg.df7cb.de> Mail-Followup-To: Christoph Berg , Giuseppe Sacco , PostgreSQL in Debian References: <831b8b45c4e1d4732aa39b41e276d49e3ea4bf59.camel@eppesuigoccas.homedns.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <831b8b45c4e1d4732aa39b41e276d49e3ea4bf59.camel@eppesuigoccas.homedns.org> User-Agent: Mutt/1.10.1 (2018-07-13) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Re: Giuseppe Sacco 2018-10-01 <831b8b45c4e1d4732aa39b41e276d49e3ea4bf59.camel@eppesuigoccas.homedns.org> > So, finally, my question: is pg_ctlcluster the root cause of my > problem? Why does it loop and wait if pg_ctl will exit anyway when the > database start or when its timeout is triggered? Should I open a bug > report for this? pg_ctlcluster originated years before systemd, so it is doing many things that should nowadays really be handled by the service file, but we haven't thrown out the old code yet. There's lots of room for improvement, yes. Christoph