| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | John Gorman <johngorman2(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | 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-28 14:43:00 |
| Message-ID: | 56D30774.2090304@dunslane.net |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
On 02/27/2016 01:24 PM, John Gorman wrote:
>
> On Sat, Feb 27, 2016 at 9:25 AM, Robert Haas <robertmhaas(at)gmail(dot)com
> <mailto:robertmhaas(at)gmail(dot)com>> wrote:
>
> On Sat, Feb 27, 2016 at 7:08 PM, Andrew Dunstan
> <andrew(at)dunslane(dot)net <mailto: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.
>
Thanks, wonderfully small patch. Applied.
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2016-02-29 04:40:55 | pgsql: Avoid multiple free_struct_lconv() calls on same data. |
| Previous Message | Andrew Dunstan | 2016-02-28 14:41:38 | pgsql: Allow multiple --temp-config arguments to pg_regress |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dilip Kumar | 2016-02-28 15:35:29 | Re: Move PinBuffer and UnpinBuffer to atomics |
| Previous Message | Craig Ringer | 2016-02-28 14:22:07 | Re: [REVIEW] In-core regression tests for replication, cascading, archiving, PITR, etc. |