From: | Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com> |
---|---|
To: | Andrey Borodin <x4mmm(at)yandex-team(dot)ru> |
Cc: | Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru>, Ivan Kartyshov <i(dot)kartyshov(at)postgrespro(dot)ru>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [Patch] Checksums for SLRU files |
Date: | 2018-07-18 05:54:44 |
Message-ID: | CAEepm=0ZFR_=QFR9KnzFkOwUbhu=J8iygk0wMxPy=NwQPq9tUQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Jul 18, 2018 at 5:41 PM, Andrey Borodin <x4mmm(at)yandex-team(dot)ru> wrote:
>> 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 found one.
> Should it be one-time test script or something "make check-world"-able?
Hi Andrey,
Like this (also reached by check-world):
$ cd src/bin/pg_upgrade
$ make check
It looks like the interesting bits are in test.sh.
--
Thomas Munro
http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Tsunakawa, Takayuki | 2018-07-18 06:09:57 | RE: [bug fix] Produce a crash dump before main() on Windows |
Previous Message | Simon Riggs | 2018-07-18 05:42:02 | Re: "Write amplification" is made worse by "getting tired" while inserting into nbtree secondary indexes (Was: Why B-Tree suffix truncation matters) |