Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1eXAR1-0000Ay-Tz for pgsql-admin@arkaria.postgresql.org; Thu, 04 Jan 2018 18:40:12 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1eXAR0-00013A-GQ for pgsql-admin@arkaria.postgresql.org; Thu, 04 Jan 2018 18:40:10 +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.84_2) (envelope-from ) id 1eXAR0-00012D-6R for pgsql-admin@lists.postgresql.org; Thu, 04 Jan 2018 18:40:10 +0000 Received: from momjian.us ([72.94.173.45]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1eXAQx-0007Lb-KW for pgsql-admin@lists.postgresql.org; Thu, 04 Jan 2018 18:40:08 +0000 Received: from bruce by momjian.us with local (Exim 4.84_2) (envelope-from ) id 1eXAQw-0007ny-5c; Thu, 04 Jan 2018 13:40:06 -0500 Date: Thu, 4 Jan 2018 13:40:06 -0500 From: Bruce Momjian To: Rob Hills Cc: pgsql-admin@lists.postgresql.org Subject: Re: pg_upgradecluster 9.5 -> 9.6 fails "Error: could not get cluster locales" on Ubuntu 17.04 Message-ID: <20180104184006.GA25056@momjian.us> References: <1c03aa8c-529e-ecaf-550c-ee8a0db28073@medimorphosis.com.au> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1c03aa8c-529e-ecaf-550c-ee8a0db28073@medimorphosis.com.au> User-Agent: Mutt/1.5.23 (2014-03-12) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On Sat, Dec 23, 2017 at 05:36:45PM +0800, Rob Hills wrote: > I tried specifying a locale in the pg_upgradecluster command but got the same > error as previously: > > sudo pg_upgradecluster --locale=en_AU.UTF-8 9.5 main > > I've found some threads discussing this specific issue, but none of them really > identify the cause or provide any workaround. > > Is there anything else I can do to try and work out what's causing the problem > and get my cluster upgraded? Since this bug looks to be in the pg_upgradecluster script, my only suggestion would be to run pg_upgrade manually. -- Bruce Momjian http://momjian.us EnterpriseDB http://enterprisedb.com + As you are, so once was I. As I am, so you will be. + + Ancient Roman grave inscription +