Re: Refactoring of pg_resetwal/t/001_basic.pl

From: Peter Eisentraut <peter(at)eisentraut(dot)org>
To: Maxim Orlov <orlovmg(at)gmail(dot)com>, Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Refactoring of pg_resetwal/t/001_basic.pl
Date: 2024-03-21 22:08:10
Message-ID: dc2a324a-8583-4748-9515-fe53553ffe4b@eisentraut.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 21.03.24 17:58, Maxim Orlov wrote:
> In commit 7b5275eec more tests and test coverage were added into
> pg_resetwal/t/001_basic.pl <http://001_basic.pl>.
> All the added stuff are pretty useful in my view.  Unfortunately, there
> were some magic constants
> been used.  In overall, this is not a problem.  But while working on 64
> bit XIDs I've noticed these
> changes and spent some time to figure it out what this magic values are
> stands fore.
>
> And it turns out that I’m not the only one.
>
> So, by Svetlana Derevyanko's suggestion, I made this patch.  I add
> constants, just like we did
> in verify_heapam tests.

Ok, this sounds like a reasonable idea.

>
> Sidenote here: in defines in multixact.c TransactionId type used, but
> I'm sure this is not correct,
> since we're dealing here with MultiXactId and MultiXactOffset.  For now,
> this is obviously not a
> problem, since sizes of this particular types are equal.  But this will
> manifest itself when we switch
> to the 64 bits types for MultiXactOffset or MultiXactId.

Please send a separate patch for this if you want to propose any changes.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Daniel Gustafsson 2024-03-21 22:10:37 Re: doc issues in event-trigger-matrix.html
Previous Message Peter Geoghegan 2024-03-21 22:05:39 Re: Optimizing nbtree ScalarArrayOp execution, allowing multi-column ordered scans, skip scan