Re: 9.6 TAP tests and extensions

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: Craig Ringer <craig(at)2ndquadrant(dot)com>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
Subject: Re: 9.6 TAP tests and extensions
Date: 2016-11-24 18:47:11
Message-ID: 20161124184711.7btc3c2lsxkdzl3t@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Craig Ringer wrote:
> On 27 October 2016 at 00:42, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> > On Wed, Oct 26, 2016 at 7:17 AM, Andres Freund <andres(at)anarazel(dot)de> wrote:
> >> On 2016-09-23 16:04:32 -0400, Tom Lane wrote:
> >>> Looking back over the thread, I see that you also proposed installing
> >>> isolationtester and pg_isolation_regress for the benefit of extensions.
> >>> I'm very much less excited about that idea. It'd be substantially more
> >>> dead weight in typical installations, and I'm not sure that it'd be useful
> >>> to common extensions, and I'm not eager to treat isolationtester's API
> >>> and behavior as something we need to hold stable for extension use.
> >>
> >> FWIW, I'd be quite happy if it were installed. Running isolationtester
> >> when compiling extensions against distribution postgres packages would
> >> be quite useful.
> >
> > +1.
>
> Patch attached.

Hmm but this only installs isolationtester itself ... don't you need
pg_isolation_regress too?

--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2016-11-24 19:36:11 Re: Declarative partitioning - another take
Previous Message Alvaro Herrera 2016-11-24 18:44:40 Re: [bugfix] commit timestamps ERROR on lookup of FrozenTransactionId