Re: Adding a test for speculative insert abort case
Andres Freund <andres@anarazel.de>
From: Andres Freund <andres@anarazel.de>
To: pgsql-hackers@lists.postgresql.org,Peter Geoghegan <pg@bowt.ie>,Melanie
Plageman <melanieplageman@gmail.com>
Cc: Pg Hackers <pgsql-hackers@postgresql.org>
Date: 2019-05-01T02:09:51Z
Lists: pgsql-hackers
Hi, On April 30, 2019 6:43:08 PM PDT, Peter Geoghegan <pg@bowt.ie> wrote: >On Tue, Apr 30, 2019 at 5:16 PM Melanie Plageman ><melanieplageman@gmail.com> wrote: >> Can anyone think of a good way to put this codepath under test? > >During the initial development of ON CONFLICT, speculative insertion >itself was tested using custom stress testing that you can still get >here: > >https://github.com/petergeoghegan/jjanes_upsert > >I'm not sure that this is something that you can adopt, but I >certainly found it very useful at the time. It tests whether or not >there is agreement among concurrent speculative inserters, and whether >or not there are "unprincipled deadlocks" (user hostile deadlocks that >cannot be fixed by reordering something in application code). I think we want a deterministic case. I recall asking for that back then... Andres -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
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