Use the right pgsql for isolation tests.

This commit is contained in:
Andrew Dunstan 2011-05-22 17:58:26 -04:00
parent 60497722ac
commit b08ddf8c76

View File

@ -6,6 +6,9 @@ subdir = src/test/isolation
top_builddir = ../../.. top_builddir = ../../..
include $(top_builddir)/src/Makefile.global include $(top_builddir)/src/Makefile.global
# where to find psql for testing an existing installation
PSQLDIR = $(bindir)
ifeq ($(PORTNAME), win32) ifeq ($(PORTNAME), win32)
LDLIBS += -lws2_32 LDLIBS += -lws2_32
endif endif
@ -70,7 +73,7 @@ maintainer-clean: distclean
rm -f specparse.c specscanner.c rm -f specparse.c specscanner.c
installcheck: all installcheck: all
./pg_isolation_regress --inputdir=$(srcdir) --schedule=$(srcdir)/isolation_schedule ./pg_isolation_regress --psqldir=$(PSQLDIR) --inputdir=$(srcdir) --schedule=$(srcdir)/isolation_schedule
# We can't support "make check" because isolationtester requires libpq, and # We can't support "make check" because isolationtester requires libpq, and
# in fact (on typical platforms using shared libraries) requires libpq to # in fact (on typical platforms using shared libraries) requires libpq to