| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, 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 15:58:50 |
| Message-ID: | 25068.1550073530@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> writes:
> On 2019-Feb-13, Tom Lane wrote:
>> Some of the slower buildfarm critters use MAX_CONNECTIONS to limit
>> the load on their hosts. As long as the isolation tests honor that,
>> I don't see a real need for a separate serial schedule.
> MAX_CONNECTIONS was the only reason I didn't push this through. Do you
> (Andres) have any solution to that?
Doesn't the common pg_regress.c infrastructure handle that?
We might need to improve isolation_main.c and/or the isolation
Makefile to make it accessible.
I suppose that in what I'm thinking about, MAX_CONNECTIONS would be
interpreted as "max number of concurrent isolation scripts", which
is not exactly number of connections. A quick and dirty answer
would be to have isolation_main.c divide the limit by a factor of 4
or so.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Gierth | 2019-02-13 16:00:57 | Re: pgsql: Change floating-point output format for improved performance. |
| Previous Message | Alvaro Herrera | 2019-02-13 15:40:08 | Re: reducing isolation tests runtime |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2019-02-13 16:48:39 | Re: Reaping Temp tables to avoid XID wraparound |
| Previous Message | Andres Freund | 2019-02-13 15:40:39 | Re: WAL insert delay settings |