From: | David Steele <david(at)pgmasters(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Michael Paquier <michael(at)paquier(dot)xyz> |
Cc: | Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: More tests to stress directly checksum_impl.h |
Date: | 2020-03-07 18:46:43 |
Message-ID: | d66d115e-fb36-6564-becc-141a9901b9e9@pgmasters.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 3/7/20 1:22 PM, Tom Lane wrote:
> Michael Paquier <michael(at)paquier(dot)xyz> writes:
>
>>> Another way would be variant output files, which could be a sane
>>> solution if we put this in its own test script.
>
> I think this way could work; see attached.
>
> I'm not sure if it's actually worth providing the variants for non-8K
> block sizes. While running the tests to construct those, I was reminded
> that not only do several of the other pageinspect tests "fail" at
> nondefault block sizes, but so do the core regression tests and some
> other tests as well. We are a long way from having check-world pass
> with nondefault block sizes, so maybe this test doesn't need to either.
> However, there's something to be said for memorializing the behavior
> we expect.
Nice! Looks like I was wrong about the checksums being the same on le/be
systems for repeated byte values. On closer inspection it looks like >>
17 at least ensures this will not be true.
Good to know.
Thanks,
--
-David
david(at)pgmasters(dot)net
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2020-03-07 18:54:57 | Re: Proposal: PqSendBuffer removal |
Previous Message | Tom Lane | 2020-03-07 18:41:58 | Re: ccache is required by postgresql12-devel RPM |