Re: PATCH pass PGOPTIONS to pg_regress

From: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
To: Manuel Kniep <m(dot)kniep(at)web(dot)de>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: PATCH pass PGOPTIONS to pg_regress
Date: 2018-06-06 15:10:11
Message-ID: 945816fc-f866-df99-d314-aa7d05d37069@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 5/29/18 09:19, Manuel Kniep wrote:
> 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

I think you can probably write this inside your test .sql file using a
bit of PL/pgSQL.

--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2018-06-06 15:17:33 Re: Why is fncollation in FunctionCallInfoData rather than fmgr_info?
Previous Message Petr Jelinek 2018-06-06 14:57:22 Re: pg_replication_slot_advance to return NULL instead of 0/0 if slot not advanced