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 1pxO8I-0007KF-9W for pgsql-hackers@arkaria.postgresql.org; Fri, 12 May 2023 08:28:10 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pxO8G-0003Mt-Ez for pgsql-hackers@arkaria.postgresql.org; Fri, 12 May 2023 08:28:08 +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 1pxO8G-0003Mk-1Z for pgsql-hackers@lists.postgresql.org; Fri, 12 May 2023 08:28:08 +0000 Received: from new2-smtp.messagingengine.com ([66.111.4.224]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1pxO8C-001tsh-8r for pgsql-hackers@postgresql.org; Fri, 12 May 2023 08:28:06 +0000 Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailnew.nyi.internal (Postfix) with ESMTP id 53B5E580424; Fri, 12 May 2023 04:28:02 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute5.internal (MEProxy); Fri, 12 May 2023 04:28:02 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:content-type:date:date:feedback-id:feedback-id :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:sender:subject:subject:to:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; t= 1683880082; x=1683887282; bh=uuu7yngEBJ077LHH8+6S4c8gvsOLEnhnTN3 /MauJwC0=; b=TlJlCrZyg4eJpydixf3glZdTipbBzXg8jmkiBNS2ZYQ9PqmcS7I kfSDMJ7GPwI1QzhaZkEozDImk43ctfL5R4xdm0aEz4CO1rOM0l7+EykGp+cpiy3E Dn5rbJfvYPFUnE4ZKTUBYyyEJeaN+26Zd72Mf+B27eVa7nl4he55fhR+rRng+rU1 K6aRFStFHF5Lig8PIVV+5HBjwwBMNQ5auyyTaqYY1ChOgB9re/elcMttBHkRiMpM QeHfLBfnOUCa18xqqdK9klmrhFh/mjso299v5KoCdBHpqZfm8LexAEIGZdsD3A41 +cKc3CuNsX6qEo1/z0B/kD9OZBRYObWLrPA== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrfeehtddgtdegucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepkfffgggfuffvvehfhfgjtgfgsehtjeertddtfeejnecuhfhrohhmpefrvght vghrucfgihhsvghnthhrrghuthcuoehpvghtvghrrdgvihhsvghnthhrrghuthesvghnth gvrhhprhhishgvuggsrdgtohhmqeenucggtffrrghtthgvrhhnpeehleffgeegudejteei hfelteduvdeifffhffdvjedvffegjeekudeludehudeifeenucevlhhushhtvghrufhiii gvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehpvghtvghrrdgvihhsvghnthhrrghu thesvghnthgvrhhprhhishgvuggsrdgtohhm X-ME-Proxy: Feedback-ID: i131946ab:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Fri, 12 May 2023 04:28:01 -0400 (EDT) Message-ID: <01bd779a-87a2-7217-a1ff-4f6d6727819a@enterprisedb.com> Date: Fri, 12 May 2023 10:28:00 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:102.0) Gecko/20100101 Thunderbird/102.10.1 Subject: Re: BUG: Postgres 14 + vacuum_defer_cleanup_age + FOR UPDATE + UPDATE Content-Language: en-US To: Andres Freund Cc: Mark Dilger , PostgreSQL Hackers References: <20230108030956.5q6ptk3boeisibjq@awork3.anarazel.de> <20230204105703.gt2j47vdn3s2gylt@alap3.anarazel.de> <20230206210205.uaaoe2l26fv256hs@awork3.anarazel.de> <20230309001558.b7shzvio645ebdta@awork3.anarazel.de> <20230311232226.fm442j4odhixy75p@awork3.anarazel.de> <20230311234121.qnlxuzijeqdxmzu2@awork3.anarazel.de> <20230510180408.bzxtaneotuy3hyk4@awork3.anarazel.de> From: Peter Eisentraut In-Reply-To: <20230510180408.bzxtaneotuy3hyk4@awork3.anarazel.de> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 10.05.23 20:04, Andres Freund wrote: >> This commit adds a test >> >> is(scalar @lp_off, $ROWCOUNT, "acquired row offsets"); >> >> *before* that skip_all call. This appears to be invalid. If the skip_all >> happens, you get a complaint like >> >> t/004_verify_heapam.pl (Wstat: 0 Tests: 1 Failed: 0) >> Parse errors: Bad plan. You planned 0 tests but ran 1. >> >> We could move the is() test after all the skip_all's. Any thoughts? > > I think the easiest fix is to just die if we can't get the offsets - it's not > like we can really continue afterwards... This should do it: -is(scalar @lp_off, $ROWCOUNT, "acquired row offsets"); +scalar @lp_off == $ROWCOUNT or BAIL_OUT("row offset counts mismatch"); But I'm not sure what the latest thinking on BAIL_OUT is. It is used nearby in a similar way though.