| 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)alvh(dot)no-ip(dot)org>, Robert Haas <robertmhaas(at)gmail(dot)com>, Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pgsql: Add parallel-aware hash joins. |
| Date: | 2018-01-24 21:01:38 |
| Message-ID: | 19481.1516827698@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:
> On 2018-01-24 15:36:35 -0500, Tom Lane wrote:
>> I'm concerned that we'd end up with a higher number of irreproducible
>> test failures with no good way to investigate them.
> Hm. We probably should dump the used ordering of tests somwhere upon
> failure, to make it easier to debug.
The progress-display output of pg_regress would need a complete rethink
anyhow. First thought is to emit two lines per test, one when we
launch it and one when it finishes and we check the results:
foreign_data: launched
...
foreign_data: ok (or FAILED)
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2018-01-24 21:07:07 | Re: pgsql: Add parallel-aware hash joins. |
| Previous Message | Tom Lane | 2018-01-24 20:58:16 | Re: pgsql: Add parallel-aware hash joins. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adam Brightwell | 2018-01-24 21:02:01 | Re: PATCH: Exclude unlogged tables from base backups |
| Previous Message | Tom Lane | 2018-01-24 20:58:16 | Re: pgsql: Add parallel-aware hash joins. |