Re: pgsql: Provide a TLS init hook

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pgsql: Provide a TLS init hook
Date: 2020-03-27 20:41:39
Message-ID: 24208.1585341699@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com> writes:
> On 3/27/20 11:09 AM, Tom Lane wrote:
>> 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.

With the makefile infrastructure, the first thing that comes to mind
is to support something like

make [install]check SKIP_TAP_TESTS=1

make [install]check SKIP_TRADITIONAL_TESTS=1

Don't know what to do in the MSVC world.

regards, tom lane

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Alvaro Herrera 2020-03-27 22:57:29 pgsql: Allow walreceiver configuration to change on reload
Previous Message Andrew Dunstan 2020-03-27 19:35:15 Re: pgsql: Provide a TLS init hook

Browse pgsql-hackers by date

  From Date Subject
Next Message Sergei Kornilov 2020-03-27 20:50:43 Re: allow online change primary_conninfo
Previous Message Andres Freund 2020-03-27 20:39:54 Re: Reinitialize stack base after fork (for the benefit of rr)?