Horton

Re: Adding a test for speculative insert abort case

Amit Kapila <amit.kapila16@gmail.com>

View thread View on postgr.es
From: Amit Kapila <amit.kapila16@gmail.com>
To: Melanie Plageman <melanieplageman@gmail.com>
Cc: Andres Freund <andres@anarazel.de>, Ashwin Agrawal <aagrawal@pivotal.io>, Pg Hackers <pgsql-hackers@postgresql.org>, Peter Geoghegan <pg@bowt.ie>, Taylor Vesely <tvesely@pivotal.io>
Date: 2020-03-24T12:33:57Z
Lists: pgsql-hackers 
On Wed, Feb 12, 2020 at 6:50 AM Melanie Plageman
<melanieplageman@gmail.com> wrote:
>
>
> On Tue, Feb 11, 2020 at 4:45 PM Andres Freund <andres@anarazel.de> wrote:
>>
>>
>> I additionally restricted the controller_print_speculative_locks step to
>> the current database and made a bunch of debug output more
>> precise. Survived ~150 runs locally.
>>
>> Lets see what the buildfarm says...
>>
>
> Thanks so much for finishing the patch and checking for race
> conditions!
>

Can we change the status of CF entry for this patch [1] to committed
or is there any work pending?


[1] - https://commitfest.postgresql.org/27/2200/
-- 
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com

Commits

  1. Test additional speculative conflict scenarios.

  2. Add isolation test for INSERT ON CONFLICT speculative insertion failure.