Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oHfGl-00064L-3L for pgsql-hackers@arkaria.postgresql.org; Sat, 30 Jul 2022 05:44:11 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1oHfGj-0004SK-Sm for pgsql-hackers@arkaria.postgresql.org; Sat, 30 Jul 2022 05:44:09 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oHfGj-0004SA-CB for pgsql-hackers@lists.postgresql.org; Sat, 30 Jul 2022 05:44:09 +0000 Received: from mail-qt1-x82c.google.com ([2607:f8b0:4864:20::82c]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1oHfGg-0006Z0-Gi for pgsql-hackers@postgresql.org; Sat, 30 Jul 2022 05:44:08 +0000 Received: by mail-qt1-x82c.google.com with SMTP id b21so4663125qte.12 for ; Fri, 29 Jul 2022 22:44:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=leadboat.com; s=google; h=user-agent:in-reply-to:content-disposition:mime-version:references :message-id:subject:cc:to:from:date:from:to:cc; bh=FlaVriD+WfaLoQGCljMxJQ3tu5BDo9+7tr+CGJMJKhM=; b=C9FCYdM1aiuKnIG3sEUSUk1RfKz84JiEiJ63i4uyBlkqZhg8GlGki3By4C+voQ9F7L 7Dnx0OxT0tLv/mdJZDL53NQ3hrfsMG1g1raOQBS+wcoJOe1pAcqM852IzeQOEsMYKL5g Dq/AssVbdvu2hhVa6HPUCgE0IWp8klzyOHhyE= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=user-agent:in-reply-to:content-disposition:mime-version:references :message-id:subject:cc:to:from:date:x-gm-message-state:from:to:cc; bh=FlaVriD+WfaLoQGCljMxJQ3tu5BDo9+7tr+CGJMJKhM=; b=faKs25Qp0V1spp1zcUnDx2E0JvfhrLrErI3HKYd0cIzi5O0C1XuzvXYJE1LCPUMXNy SwZ4Sf7tEom4wtzZWD6N9aORqibNW3DWHkCKk1TTbbP4RT+9JSYoek4R7CjpF3FBMPDm e5q/afbgdW/+qAG2/MVNfoU6Elz/w4nrxyZb4JlW38EXv/EAR4pbFZo63KbpRs4MWYrX g+aGajjUnScJ+3Lq+qjWZY5hgCB/jdsxK8+Cyz2Yxc4XLwmpkMBb68s3hUwlv+D3vLsU 0H0LxgHh1yul+ZtqOEXEBngF5DCPmaF1Z/366Fy9Ap4K7IuL6DGocjWZogjWkddC/GJd 1zNw== X-Gm-Message-State: AJIora/zCy8vUlmC98298iEYNavdm0TVvCcbJYk32vktm6OrQJ2aDR5H WzNFICYSftTlXrHsmsoZgZjjPA== X-Google-Smtp-Source: AGRyM1vEtZys4qdHCQuuVdUISTJpfybKU9KcRbxP7vIQm8UE7J4zwWlgkvj0+hNI0Nu2i+uhuOnQcA== X-Received: by 2002:a05:622a:1453:b0:31f:4542:db80 with SMTP id v19-20020a05622a145300b0031f4542db80mr6179385qtx.570.1659159845534; Fri, 29 Jul 2022 22:44:05 -0700 (PDT) Received: from rfd.leadboat.com ([2600:1702:a20:5750::2e]) by smtp.gmail.com with ESMTPSA id h3-20020a05620a400300b006b5da3c8d81sm4080871qko.73.2022.07.29.22.44.03 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 29 Jul 2022 22:44:04 -0700 (PDT) Date: Fri, 29 Jul 2022 22:44:01 -0700 From: Noah Misch To: Robert Haas , Tom Lane Cc: Andrew Dunstan , Bruce Momjian , Michael Paquier , Justin Pryzby , "pgsql-hackers@postgresql.org" , Shruthi Gowda Subject: Re: pg15b2: large objects lost on upgrade Message-ID: <20220730054401.GB3644221@rfd.leadboat.com> References: <3901843.1659116952@sss.pgh.pa.us> <4152163.1659124804@sss.pgh.pa.us> <125444.1659136594@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <125444.1659136594@sss.pgh.pa.us> User-Agent: Mutt/1.5.24 (2015-08-30) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Fri, Jul 29, 2022 at 07:16:34PM -0400, Tom Lane wrote: > Robert Haas writes: > > wrasse just failed the new test: > > > [00:09:44.167](0.001s) not ok 16 - old and new horizons match after pg_upgrade > > [00:09:44.167](0.001s) > > [00:09:44.167](0.000s) # Failed test 'old and new horizons match > > after pg_upgrade' > > # at t/002_pg_upgrade.pl line 345. > > [00:09:44.168](0.000s) # got: '1' > > # expected: '0' > > === diff of /export/home/nm/farm/studio64v12_6/HEAD/pgsql.build/src/bin/pg_upgrade/tmp_check/tmp_test_D3cJ/horizon1.txt > > and /export/home/nm/farm/studio64v12_6/HEAD/pgsql.build/src/bin/pg_upgrade/tmp_check/tmp_test_D3cJ/horizon2.txt > > === stdout === > > 1c1 > > < pg_backend_pid|21767 > > --- > > > pg_backend_pid|22045=== stderr === > > === EOF === > > > I'm slightly befuddled as to how we're ending up with a table named > > pg_backend_pid. > The lack of -X and the lack of use of installed_command() > are red flags. The pg_backend_pid is from "SELECT pg_catalog.pg_backend_pid();" in ~/.psqlrc, so the lack of -X caused that. The latest commit fixes things on a normal GNU/Linux box, so I bet it will fix wrasse. (thorntail managed not to fail that way. For unrelated reasons, I override thorntail's $HOME to a mostly-empty directory.)