From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
---|---|
To: | Alexander Korotkov <aekorotkov(at)gmail(dot)com> |
Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: POC: Better infrastructure for automated testing of concurrency issues |
Date: | 2020-12-04 18:29:51 |
Message-ID: | 20201204182951.GA2183@alvherre.pgsql |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 2020-Nov-25, Alexander Korotkov wrote:
> In the view of above, I'd like to propose a POC patch, which implements new
> builtin infrastructure for reproduction of concurrency issues in automated
> test suites. The general idea is so-called "stop events", which are
> special places in the code, where the execution could be stopped on some
> condition. Stop event also exposes a set of parameters, encapsulated into
> jsonb value. The condition over stop event parameters is defined using
> jsonpath language.
+1 for the idea. I agree we have a need for something on this area;
there are *many* scenarios currently untested because of the lack of
what you call "stop points". I don't know if jsonpath is the best way
to implement it, but at least it is readily available and it seems a
decent way to go at it.
From | Date | Subject | |
---|---|---|---|
Next Message | Alexey Kondratov | 2020-12-04 18:40:31 | Re: Allow CLUSTER, VACUUM FULL and REINDEX to change tablespace on the fly |
Previous Message | Euler Taveira | 2020-12-04 18:28:20 | Re: Logical archiving |