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 1fSqbf-00073x-A3 for pgsql-admin@arkaria.postgresql.org; Tue, 12 Jun 2018 21:13:35 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1fSqbd-0006Xf-Qk for pgsql-admin@arkaria.postgresql.org; Tue, 12 Jun 2018 21:13:33 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1fSqbd-0006XP-JF; Tue, 12 Jun 2018 21:13:33 +0000 Received: from out1-smtp.messagingengine.com ([66.111.4.25]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1fSqba-0000vJ-C4; Tue, 12 Jun 2018 21:13:32 +0000 Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id E3F2121B25; Tue, 12 Jun 2018 17:13:28 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute6.internal (MEProxy); Tue, 12 Jun 2018 17:13:28 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aklaver.com; h= content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm3; bh=Q647qB/EsUs1n+eC2am/QmHlSXfIb qQLGmnGpnKCOIg=; b=0AvQajslYkQDtTBghqoVf39DRBUJP5cWiOsO8SpgVmb+P S/T8kalS734sUgVBQol8ayd54Zrr6LImD7MDzrhxfl2ZPc6OEkcKgzUwGBmCpcdA /SvlznVo2SXUgiMDq5o5w03cpNd4GJmiF3OHVZ87Mdc2SbQMbk324HN1E+3bzLfh AGVcK41ht6lPMyXzfTKliOBl2riGWnDe5Oq98AmfQ8qMyeN07zIotYQp01Tr8Uhu 18ZHnO6Rr4/SUGc1ItJv4pvJVag9uB/1ikcnGC3fngn6LD5pXBnrn+GG5wsZJXex s2BnHey8o45DEbpammQTlDCJ8baGe43VGRVsluVOg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=Q647qB /EsUs1n+eC2am/QmHlSXfIbqQLGmnGpnKCOIg=; b=NeqfmF/NwBVZCMozvPGeNG WK6Qdl3ZEWmWJkOxQed0mZqmQvTIuUibOoTcb8ndsj/tO1Kvc7bftuPE1yoXVMuY sUVFktnss+mVDsVdLKVkx78rFxBBM78t6a0ll3zSV6PRbo2pW/q6vIc1WFqWxXuU 12DcRrh1DY9X591eYH+jBFw2oJs80vNUmDFL1vAnfir63zwnFFf5zX6FCzcnd8/W mwpRBHhEl4i47GDjrRDbjlBs+AORp1n33t8ok1UWq0O7fFJudUH7D5PSy1iRhHhp XA2p2Kyb1W0m+yRvqHydSKH08PiJciA/aVV463ZA3/MRzFOmNpV+UtmVlJfSlt5A == X-ME-Proxy: X-ME-Proxy: X-ME-Proxy: X-ME-Proxy: X-ME-Proxy: X-ME-Proxy: X-ME-Sender: Received: from ranger.suse (c-73-239-117-238.hsd1.wa.comcast.net [73.239.117.238]) by mail.messagingengine.com (Postfix) with ESMTPA id 169EDE469E; Tue, 12 Jun 2018 17:13:27 -0400 (EDT) Subject: Re: pg_upgrade 10.2 To: Murthy Nunna , "pgsql-general@lists.postgresql.org" , "pgsql-admin@lists.postgresql.org" , "pgsql-performance@lists.postgresql.org" References: <1a3ebd40-7870-3eab-97d4-ca2b9907d917@aklaver.com> From: Adrian Klaver Message-ID: <5f0d7335-e681-56bb-7d14-cf97fccb1bcf@aklaver.com> Date: Tue, 12 Jun 2018 14:13:27 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On 06/12/2018 01:58 PM, Murthy Nunna wrote: > Thanks Adrian. > I removed "-k" flag. But still got same error. > > There seems to be a postmaster servicing the old cluster. > Please shutdown that postmaster and try again. > Failure, exiting > Well according to the code in pg_upgrade.c that message should not be reached when the check option is specified: if (!user_opts.check) pg_fatal("There seems to be a postmaster servicing the old cluster.\n" "Please shutdown that postmaster and try again.\n"); else *live_check = true; Can we see the actual command you ran? -- Adrian Klaver adrian.klaver@aklaver.com