Re: Fix bloom WAL tap test
Alexander Korotkov <a.korotkov@postgrespro.ru>
From: Alexander Korotkov <a.korotkov@postgrespro.ru>
To: Masahiko Sawada <sawada.mshk@gmail.com>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2017-11-07T16:58:35Z
Lists: pgsql-hackers
Hi! On Tue, Nov 7, 2017 at 4:34 PM, Masahiko Sawada <sawada.mshk@gmail.com> wrote: > I understood the necessity of this patch and reviewed two patches. > Good, thank you. > For /fix-bloom-wal-check.patch, it looks good to me. I found no > problem. But for wal-check-on-bloom-check.patch, if you want to run > wal-check even when running 'make check' or 'make check-world', we can > just add wal-check test as follows? > > diff --git a/contrib/bloom/Makefile b/contrib/bloom/Makefile > index 13bd397..c1566d4 100644 > --- a/contrib/bloom/Makefile > +++ b/contrib/bloom/Makefile > @@ -20,5 +20,7 @@ include $(top_builddir)/src/Makefile.global > include $(top_srcdir)/contrib/contrib-global.mk > endif > > +check: wal-check > + > wal-check: temp-install > $(prove_check) > I've tried this version Makefile. And I've seen the only difference: when tap tests are enabled, this version of Makefile runs tap tests before regression tests. While my version of Makefile runs tap tests after regression tests. That seems like more desirable behavior for me. But it would be sill nice to simplify Makefile. ------ Alexander Korotkov Postgres Professional: http://www.postgrespro.com The Russian Postgres Company
Commits
-
Tighten test in contrib/bloom/t/001_wal.pl.
- 859662c26cf9 9.6.7 landed
- d33fc27e8df6 10.2 landed
- 7e60e678615b 11.0 landed