Re: Very confusing installcheck behavior with PGXS - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Very confusing installcheck behavior with PGXS
Date
Msg-id 12108.1452178021@sss.pgh.pa.us
Whole thread Raw
In response to Re: Very confusing installcheck behavior with PGXS  (Jim Nasby <Jim.Nasby@BlueTreble.com>)
Responses Re: Very confusing installcheck behavior with PGXS  (Jim Nasby <Jim.Nasby@BlueTreble.com>)
List pgsql-hackers
Jim Nasby <Jim.Nasby@BlueTreble.com> writes:
> However, if I do this:
> mv test/sql/acl_type.sql test/sql/acl.sql
> mv test/expected/acl_type.out test/expected/acl.out

> And change acl_type to acl in that pg_regress command:
> /Users/decibel/pgsql/HEAD/i/lib/pgxs/src/makefiles/../../src/test/regress/pg_regress 
> --bindir='/Users/decibel/pgsql/HEAD/i/bin' --inputdir=test 
> --load-language=plpgsql --dbname=contrib_regression acl build compat rights

> Instead of executing test/sql/acl.sql, it executes ./sql/acl.sql.

That's pretty hard to believe.  There's nothing in pg_regress that looks
in places other than the given --inputdir.

I wonder whether you have a test/input/acl.sql and/or test/output/acl.out
that's confusing matters.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Joel Jacobson
Date:
Subject: Re: Proposal: "Causal reads" mode for load balancing reads without stale data
Next
From: Jim Nasby
Date:
Subject: Re: Very confusing installcheck behavior with PGXS