2016-04-01 21:42:24 +08:00
|
|
|
# contrib/bloom/Makefile
|
|
|
|
|
|
|
|
MODULE_big = bloom
|
2019-11-06 06:41:07 +08:00
|
|
|
OBJS = \
|
|
|
|
$(WIN32RES) \
|
|
|
|
blcost.o \
|
|
|
|
blinsert.o \
|
|
|
|
blscan.o \
|
|
|
|
blutils.o \
|
|
|
|
blvacuum.o \
|
|
|
|
blvalidate.o
|
2016-04-01 21:42:24 +08:00
|
|
|
|
|
|
|
EXTENSION = bloom
|
|
|
|
DATA = bloom--1.0.sql
|
|
|
|
PGFILEDESC = "bloom access method - signature file based index"
|
|
|
|
|
|
|
|
REGRESS = bloom
|
2018-11-26 08:42:21 +08:00
|
|
|
|
Add PGXS options to control TAP and isolation tests, take two
The following options are added for extensions:
- TAP_TESTS, to allow an extention to run TAP tests which are the ones
present in t/*.pl. A subset of tests can always be run with the
existing PROVE_TESTS for developers.
- ISOLATION, to define a list of isolation tests.
- ISOLATION_OPTS, to pass custom options to isolation_tester.
A couple of custom Makefile rules have been accumulated across the tree
to cover the lack of facility in PGXS for a couple of releases when
using those test suites, which are all now replaced with the new flags,
without reducing the test coverage. Note that tests of contrib/bloom/
are not enabled yet, as those are proving unstable in the buildfarm.
Author: Michael Paquier
Reviewed-by: Adam Berlin, Álvaro Herrera, Tom Lane, Nikolay Shaplov,
Arthur Zakirov
Discussion: https://postgr.es/m/20180906014849.GG2726@paquier.xyz
2018-12-03 08:27:35 +08:00
|
|
|
# Disable TAP tests for this module for now, as these are unstable on several
|
|
|
|
# buildfarm environments.
|
|
|
|
# TAP_TESTS = 1
|
|
|
|
|
2016-04-01 21:42:24 +08:00
|
|
|
ifdef USE_PGXS
|
|
|
|
PG_CONFIG = pg_config
|
|
|
|
PGXS := $(shell $(PG_CONFIG) --pgxs)
|
|
|
|
include $(PGXS)
|
|
|
|
else
|
|
|
|
subdir = contrib/bloom
|
|
|
|
top_builddir = ../..
|
|
|
|
include $(top_builddir)/src/Makefile.global
|
|
|
|
include $(top_srcdir)/contrib/contrib-global.mk
|
|
|
|
endif
|