From: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | 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-14 06:55:18 |
Message-ID: | CAMsr+YEpg0rwKVjuV7grd+VrLDWKba3Pz=FRy5GkzKpxeAVPcg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
Attachment | Content-Type | Size |
---|---|---|
0001-Install-isolationtester.patch | text/x-patch | 1.4 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Craig Ringer | 2016-11-14 07:01:35 | [PATCH] PostgresNode.pm enhancements, pg_lsn helper, and some more recovery tests |
Previous Message | Craig Ringer | 2016-11-14 06:45:37 | Re: [PATCH] Allow TAP tests to be run individually |