Re: Adding a test for speculative insert abort case

Melanie Plageman <melanieplageman@gmail.com>

From: Melanie Plageman <melanieplageman@gmail.com>
To: Andres Freund <andres@anarazel.de>
Cc: Ashwin Agrawal <aagrawal@pivotal.io>, Pg Hackers <pgsql-hackers@postgresql.org>, Peter Geoghegan <pg@bowt.ie>, Taylor Vesely <tvesely@pivotal.io>
Date: 2020-02-12T01:20:05Z
Lists: pgsql-hackers
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!

-- 
Melanie Plageman

Commits

  1. Test additional speculative conflict scenarios.

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