Re: [Patch] Checksums for SLRU files - Mailing list pgsql-hackers

From Andrey Borodin
Subject Re: [Patch] Checksums for SLRU files
Date
Msg-id D2C2E05C-B5A1-4488-8FF8-129286A84EE8@yandex-team.ru
Whole thread Raw
In response to Re: [Patch] Checksums for SLRU files  (Thomas Munro <thomas.munro@enterprisedb.com>)
Responses Re: [Patch] Checksums for SLRU files  (Thomas Munro <thomas.munro@enterprisedb.com>)
List pgsql-hackers
Hi, Tomas!

>
> I think we'd want pg_upgrade tests showing an example of each SLRU
> growing past one segment, and then being upgraded, and then being
> accessed in various different pages and segment files, so that we can
> see that we're able to shift the data to the right place successfully.
> For example I think I'd want to see that a single aborted transaction
> surrounded by many committed transactions shows up in the right place
> after an upgrade.

Can you elaborate a bit on how to implement this test. I've searched for some automated pg_upgrade tests but didn't
foundone. 
Should it be one-time test script or something "make check-world"-able?

Best regards, Andrey Borodin.

pgsql-hackers by date:

Previous
From: Masahiko Sawada
Date:
Subject: print_path is missing GatherMerge and CustomScan support
Next
From: Simon Riggs
Date:
Subject: Re: "Write amplification" is made worse by "getting tired" whileinserting into nbtree secondary indexes (Was: Why B-Tree suffix truncation matters)