| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
| Cc: | Dilip Kumar <dilipbalaut(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, mailings(at)oopsware(dot)de, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pg_verify_checksums failure with hash indexes |
| Date: | 2018-09-05 04:16:00 |
| Message-ID: | 20470.1536120960@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Amit Kapila <amit(dot)kapila16(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2018-09-05 04:29:07 | Re: Prevent concurrent DROP SCHEMA when certain objects are being initially created in the namespace |
| Previous Message | Tom Lane | 2018-09-05 04:11:25 | Re: Prevent concurrent DROP SCHEMA when certain objects are being initially created in the namespace |