pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Peter Eisentraut <peter.eisentraut@enterprisedb.com>
To: Andres Freund <andres@anarazel.de>
Cc: Mark Dilger <mark.dilger@enterprisedb.com>
Cc: PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Subject: Re: BUG: Postgres 14 + vacuum_defer_cleanup_age + FOR UPDATE + UPDATE
Date: Fri, 12 May 2023 10:28:00 +0200
Message-ID: <01bd779a-87a2-7217-a1ff-4f6d6727819a@enterprisedb.com> (raw)
In-Reply-To: <20230510180408.bzxtaneotuy3hyk4@awork3.anarazel.de>
References: <20230108030956.5q6ptk3boeisibjq@awork3.anarazel.de>
	<20230204105703.gt2j47vdn3s2gylt@alap3.anarazel.de>
	<CAH2-Wzkrh1OmRy=xNQbx4Yb708j152tZ-oPKS1S7fNURVxKTOg@mail.gmail.com>
	<20230206210205.uaaoe2l26fv256hs@awork3.anarazel.de>
	<20230309001558.b7shzvio645ebdta@awork3.anarazel.de>
	<E244808B-83A5-4E50-93BF-DF8D5544505A@enterprisedb.com>
	<20230311232226.fm442j4odhixy75p@awork3.anarazel.de>
	<ED5BB5D4-4C4D-4838-8D42-3A03CFB16791@enterprisedb.com>
	<20230311234121.qnlxuzijeqdxmzu2@awork3.anarazel.de>
	<af5567a1-aea6-fbdb-7e4b-d1e23a43c43b@enterprisedb.com>
	<20230510180408.bzxtaneotuy3hyk4@awork3.anarazel.de>

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.






view thread (38+ messages)  latest in thread

Message-ID: <01bd779a-87a2-7217-a1ff-4f6d6727819a@enterprisedb.com>
Permalink:  ../01bd779a-87a2-7217-a1ff-4f6d6727819a@enterprisedb.com/
Also on:    postgresql.org/message-id/01bd779a-87a2-7217-a1ff-4f6d6727819a@enterprisedb.com

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: peter.eisentraut@enterprisedb.com, andres@anarazel.de, mark.dilger@enterprisedb.com
  Subject: Re: BUG: Postgres 14 + vacuum_defer_cleanup_age + FOR UPDATE + UPDATE
  In-Reply-To: <01bd779a-87a2-7217-a1ff-4f6d6727819a@enterprisedb.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox