Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1ZjT3H-000126-JW for pgsql-admin@arkaria.postgresql.org; Tue, 06 Oct 2015 14:17:11 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84) (envelope-from ) id 1ZjT3H-0002sU-5x for pgsql-admin@arkaria.postgresql.org; Tue, 06 Oct 2015 14:17:11 +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) (envelope-from ) id 1ZjT1b-00077Y-94 for pgsql-admin@postgresql.org; Tue, 06 Oct 2015 14:15:27 +0000 Received: from momjian.us ([72.94.173.45]) by makus.postgresql.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:256) (Exim 4.84) (envelope-from ) id 1ZjT1Y-0005yT-FO for pgsql-admin@postgresql.org; Tue, 06 Oct 2015 14:15:26 +0000 Received: from bruce by momjian.us with local (Exim 4.72) (envelope-from ) id 1ZjT1X-0008UE-EE; Tue, 06 Oct 2015 10:15:23 -0400 Date: Tue, 6 Oct 2015 10:15:23 -0400 From: Bruce Momjian To: "Guo, Yun" Cc: "pgsql-admin@postgresql.org" Subject: Re: pg_upgrade from 9.3 to 9.4 fails Message-ID: <20151006141523.GC9625@momjian.us> References: <20151005172418.GA6784@momjian.us> <20151005180244.GB6784@momjian.us> <20151005181612.GC6784@momjian.us> <20151005190218.GD6784@momjian.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) X-Pg-Spam-Score: -1.9 (-) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-admin Precedence: bulk Sender: pgsql-admin-owner@postgresql.org On Mon, Oct 5, 2015 at 07:44:51PM +0000, Guo, Yun wrote: > >My only guess is that when the server is running, you have started it > >with some special options that pg_upgrade doesn't know about. If the > >server is down, pg_upgrade has to start it to check it, and that might > >be causing the problem. It would also be good to know if the failure is > >with the old or new cluster. > > pg_upgrade_server.log outputs below message: So you get the error: ERROR: cache lookup failed for type 1670699 from pg_upgrade starting the server, but not when the server is already running? I can't even guess what is wrong. -- Bruce Momjian http://momjian.us EnterpriseDB http://enterprisedb.com + As you are, so once was I. As I am, so you will be. + + Roman grave inscription + -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin