Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1h60t2-0002Tv-2e for pgsql-bugs@arkaria.postgresql.org; Mon, 18 Mar 2019 22:37:40 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1h60sz-0005p1-NH for pgsql-bugs@arkaria.postgresql.org; Mon, 18 Mar 2019 22:37:37 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1h60sz-0005ks-8V for pgsql-bugs@lists.postgresql.org; Mon, 18 Mar 2019 22:37:37 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1h60ss-0001hd-FY for pgsql-bugs@lists.postgresql.org; Mon, 18 Mar 2019 22:37:35 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id x2IMbSqL007303; Mon, 18 Mar 2019 18:37:28 -0400 From: Tom Lane To: Tomasz Szypowski cc: pgsql-bugs@lists.postgresql.org Subject: Re: pg_upgrade In-reply-to: References: <2267.1552919581@sss.pgh.pa.us> <5834.1552946317@sss.pgh.pa.us> Comments: In-reply-to Tomasz Szypowski message dated "Mon, 18 Mar 2019 23:05:54 +0100" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <7301.1552948648.1@sss.pgh.pa.us> Date: Mon, 18 Mar 2019 18:37:28 -0400 Message-ID: <7302.1552948648@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Tomasz Szypowski writes: > So what set it to false? I was hoping you'd tell me ;-). If it's not false in the old cluster, though, that theory is all wet. I wonder if you're somehow using the wrong version of pg_upgrade or pg_dump. There are cross-checks about that in pg_upgrade, but it looks like they only check the major version number --- if we'd changed anything about this in a minor release (which I think we did), it might be possible to get burnt if you were using pg_upgrade or pg_dump from a prior minor release. What are all the versions involved, exactly? regards, tom lane