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

From Tom Lane
Subject Re: pg_verify_checksums failure with hash indexes
Date
Msg-id 20470.1536120960@sss.pgh.pa.us
Whole thread Raw
In response to Re: pg_verify_checksums failure with hash indexes  (Amit Kapila <amit.kapila16@gmail.com>)
Responses Re: pg_verify_checksums failure with hash indexes  (Amit Kapila <amit.kapila16@gmail.com>)
Re: pg_verify_checksums failure with hash indexes  (Michael Paquier <michael@paquier.xyz>)
List pgsql-hackers
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.

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.

            regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Prevent concurrent DROP SCHEMA when certain objects are being initially created in the namespace
Next
From: Andres Freund
Date:
Subject: Re: Prevent concurrent DROP SCHEMA when certain objects are being initially created in the namespace