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>
Date: 2019-06-05T22:49:47Z
Lists: pgsql-hackers
Attachments
- v2-0002-Add-TOAST-case-to-spec-conflict-tests.patch (text/x-patch) patch v2-0002
- v2-0001-Test-speculative-wait-case.patch (text/x-patch) patch v2-0001
On Thu, May 16, 2019 at 8:46 PM Melanie Plageman <melanieplageman@gmail.com> wrote: > > Good idea. > I squashed the changes I suggested in previous emails, Ashwin's patch, my > suggested updates to that patch, and the index order check all into one > updated > patch attached. > > I've updated this patch to make it apply on master cleanly. Thanks to Alvaro for format-patch suggestion. The first patch in the set adds the speculative wait case discussed above from Ashwin's patch. The second patch in the set is another suggestion I have. I noticed that the insert-conflict-toast test mentions that it is "not guaranteed to lead to a failed speculative insertion" and, since it seems to be testing the speculative abort but with TOAST tables, I thought it might work to kill that spec file and move that test case into insert-conflict-specconflict so the test can utilize the existing advisory locks being used for the other tests in that file to make it deterministic which session succeeds in inserting the tuple. -- Melanie Plageman
Commits
-
Test additional speculative conflict scenarios.
- 43e08419708a 13.0 landed
-
Add isolation test for INSERT ON CONFLICT speculative insertion failure.
- 0491a51fdd4e 9.6.14 landed
- 04595960a0a7 10.9 landed
- 05cf41973157 11.4 landed
- 08e2edc0767a 12.0 landed