| From: | Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pgsql: Provide a TLS init hook |
| Date: | 2020-03-27 19:35:15 |
| Message-ID: | 459bb9e4-d4d7-baaf-76f2-65f7171fab0c@2ndQuadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
On 3/27/20 11:09 AM, Tom Lane wrote:
>
>> Right now the explicit TAP test code in the buildfarm knows how to collect all the relevant output. The installcheck code doesn't know about that for TAP tests.
> It seems like what the buildfarm would like is a way to invoke TAP tests
> and traditional-framework tests separately, so that it could apply special
> tooling to the former. I'd have no objection to making that possible.
>
Exactly. I'll look into that, but I'm open to any ideas people have.
cheers
andrew
--
Andrew Dunstan https://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2020-03-27 20:41:39 | Re: pgsql: Provide a TLS init hook |
| Previous Message | Alvaro Herrera | 2020-03-27 19:24:59 | pgsql: Set wal_receiver_create_temp_slot PGC_POSTMASTER |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2020-03-27 19:48:50 | Re: backup manifests |
| Previous Message | Robert Haas | 2020-03-27 19:29:02 | Re: backup manifests |