| From: | Ildar Musin <i(dot)musin(at)postgrespro(dot)ru> |
|---|---|
| To: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: PATCH pass PGOPTIONS to pg_regress |
| Date: | 2018-05-30 09:28:27 |
| Message-ID: | 376f1047-93cb-311f-7178-117ad4881f4b@postgrespro.ru |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi Manuel,
On 29.05.2018 16:19, Manuel Kniep wrote:
> Hi,
>
> attached patch passes PGOPTIONS env variable to pg_regress in
> pgxs.mk
>
> This is especially useful when developing extensions for different
> postgres versions where some session_variables might or might not
> exists.
>
> Consider something like this in an extensions makefile:
>
> ifeq ($(shell test $(VERSION_NUM) -ge 90600; echo $$?),0) PGOPTIONS+=
> "--max_parallel_workers_per_gather=0" endif
>
> But also when there are many testfiles it might be convenient to
> align some session parameter globally In the Makefile.
Have you considered using EXTRA_REGRESS_OPTS variable in extension's
Makefile?
EXTRA_REGRESS_OPTS=--temp-config=$(top_srcdir)/$(subdir)/extra.conf
Here extra.conf is implied to be a file in extension's root directory
which contains additional server options.
This would only work for `make check` though, not `make installcheck`.
--
Ildar Musin
i(dot)musin(at)postgrespro(dot)ru
| From | Date | Subject | |
|---|---|---|---|
| Next Message | REIX, Tony | 2018-05-30 09:50:45 | PostgreSQL 11 beta1 on AIX 7.2 : 2 failures in 32bit mode |
| Previous Message | Antonin Houska | 2018-05-30 07:26:33 | Incorrect visibility test function assigned to snapshot |