Re: [PATCH] We install pg_regress and isolationtester but not pg_isolation_regress - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [PATCH] We install pg_regress and isolationtester but not pg_isolation_regress
Date
Msg-id 2955933.1619664098@sss.pgh.pa.us
Whole thread Raw
In response to Re: [PATCH] We install pg_regress and isolationtester but not pg_isolation_regress  (Michael Paquier <michael@paquier.xyz>)
Responses Re: [PATCH] We install pg_regress and isolationtester but not pg_isolation_regress  (Magnus Hagander <magnus@hagander.net>)
List pgsql-hackers
Michael Paquier <michael@paquier.xyz> writes:
> On Wed, Apr 28, 2021 at 12:44:45PM +0300, Aleksander Alekseev wrote:
>> I just wanted to let you know that TimescaleDB uses
>> pg_isolation_regress and occasionally there are reports from some
>> suffering/puzzled users/developers, e.g. [1]. Not 100% sure if it
>> makes investing the time into backpatching worth it. However if
>> someone could do it, it would be nice.

> FWIW, I am not really sure that this is important enough to justify a
> back-patch, even it is true that there have been cases in the past
> where extra binaries got added in minor releases.

Yeah, I think adding a binary in a minor release is a Big Deal to
packagers.  I doubt that the case here justifies that.

            regards, tom lane



pgsql-hackers by date:

Previous
From: "tanghy.fnst@fujitsu.com"
Date:
Subject: [BUG]"FailedAssertion" reported in lazy_scan_heap() when running logical replication
Next
From: Michael Paquier
Date:
Subject: Re: [BUG]"FailedAssertion" reported in lazy_scan_heap() when running logical replication