| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: reducing isolation tests runtime |
| Date: | 2019-02-13 17:41:41 |
| Message-ID: | 29883.1550079701@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
Andres Freund <andres(at)anarazel(dot)de> writes:
> Do you have an idea why we have both max_concurrent_tests *and*
> max_connections in pg_regress? ISTM the former isn't really useful given
> the latter?
No, the former is a static restriction on what the schedule file is
allowed to contain, the latter is a dynamic restriction (that typically
is unlimited anyway).
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2019-02-13 17:46:50 | Re: reducing isolation tests runtime |
| Previous Message | Andres Freund | 2019-02-13 17:03:39 | Re: reducing isolation tests runtime |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2019-02-13 17:41:51 | Re: subscriptionCheck failures on nightjar |
| Previous Message | Tom Lane | 2019-02-13 17:37:35 | Re: subscriptionCheck failures on nightjar |