Postgres Pro
Downloads
Home   >   mailing lists

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

From Aleksander Alekseev
Subject Re: [PATCH] We install pg_regress and isolationtester but not pg_isolation_regress
Date
Msg-id CAJ7c6TOC_LpKd-4GFZ7J=mPtPgh7G8=PbBzHBhw0mAnQVu=UiQ@mail.gmail.com
Whole thread Raw
In response to Re: [PATCH] We install pg_regress and isolationtester but not pg_isolation_regress  (Craig Ringer <craig.ringer@enterprisedb.com>)
Responses Re: [PATCH] We install pg_regress and isolationtester but not pg_isolation_regress  (Michael Paquier <michael@paquier.xyz>)
List pgsql-hackers
Tree view 
Hi hackers,

> Any opinions on backpatching?

> Other than src/test/modules/brin, the ISOLATION users don't look
> much like real extensions (rather than test scaffolding), either.

> Out of core, the only thing I can see with isolation tests is rum, but
> it uses a workaround to have an access to the necessary binaries.

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.

[1]: https://github.com/timescale/timescaledb/issues/1655

-- 
Best regards,
Aleksander Alekseev

pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: Replication slot stats misgivings
Next
From: Antonin Houska
Date:
Subject: Re: Built-in connection pooler