Re: pg_verify_checksums failure with hash indexes - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: pg_verify_checksums failure with hash indexes
Date
Msg-id 20180905182813.GE2726@paquier.xyz
Whole thread Raw
In response to Re: pg_verify_checksums failure with hash indexes  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Wed, Sep 05, 2018 at 12:16:00AM -0400, Tom Lane wrote:
> Amit Kapila <amit.kapila16@gmail.com> writes:
>> Does anybody else have any idea on how can we write a test for
>> non-default block size or if we already have anything similar?
>
> Build with a non-default BLCKSZ and see if the regression tests pass.
> There's no way that a build with BLCKSZ x can run any tests for
> BLCKSZ y.

Or we could implement block-level configuration at initdb time?  That's
what Andres has done for WAL segment size recently.

/me hides and runs fast

> Note that you can expect some plan variations from a different BLCKSZ,
> so there'd be at least a few "failures" in the regression tests, which'd
> require manual inspection. Otherwise this could be delegated to a
> buildfarm animal using a nonstandard BLCKSZ.

Last time I did that I saw only plan diffs, which was a couple of weeks
ago.
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: pgsql: Clean up after TAP tests in oid2name and vacuumlo.
Next
From: Andres Freund
Date:
Subject: Re: JIT compiling with LLVM v12