| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Very confusing installcheck behavior with PGXS |
| Date: | 2016-01-07 14:47:01 |
| Message-ID: | 12108.1452178021@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim Nasby | 2016-01-07 14:50:50 | Re: Very confusing installcheck behavior with PGXS |
| Previous Message | Joel Jacobson | 2016-01-07 14:40:14 | Re: Proposal: "Causal reads" mode for load balancing reads without stale data |