| From: | John Gorman <johngorman2(at)gmail(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, Andres Freund <andres(at)anarazel(dot)de>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Re: [COMMITTERS] pgsql: Respect TEMP_CONFIG when running contrib regression tests. |
| Date: | 2016-02-27 18:24:09 |
| Message-ID: | CALkS6B_u3AH6H1jWCH1pDTc_hiG5TqXDW8hzxP190Boe8nD03Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
On Sat, Feb 27, 2016 at 9:25 AM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> On Sat, Feb 27, 2016 at 7:08 PM, Andrew Dunstan <andrew(at)dunslane(dot)net>
> wrote:
>
> > Perhaps what we need to do is modify pg_regress.c slightly to allow more
> > than one --temp-config argument. But that could be done later.
>
> Well, I'm pretty interested in using --temp-config for parallelism
> testing; I want to be able to run the whole regression test suite with
> a given --temp-config. I'm in agreement with this change but if it
> doesn't play well with that need, I suppose I'll be writing that
> pg_regress.c patch sooner rather than later.
Here is a patch to allow pg_regress to include several --temp-config files.
| Attachment | Content-Type | Size |
|---|---|---|
| pg_regress-temp-configs-v1.patch | application/octet-stream | 1.2 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2016-02-28 14:41:38 | pgsql: Allow multiple --temp-config arguments to pg_regress |
| Previous Message | Andrew Dunstan | 2016-02-27 17:32:04 | pgsql: Respect TEMP_CONFIG when pg_regress_check and friends are called |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Álvaro Hernández Tortosa | 2016-02-27 18:51:27 | Re: PostgreSQL extension API? Documentation? |
| Previous Message | Kevin Grittner | 2016-02-27 17:54:37 | Re: The plan for FDW-based sharding |