| From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
|---|---|
| To: | Melanie Plageman <melanieplageman(at)gmail(dot)com> |
| Cc: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Adding a test for speculative insert abort case |
| Date: | 2019-05-01 01:43:08 |
| Message-ID: | CAH2-WzmzQX_z9Kct1GWEnz=zR0VQeRMoyT4S1Tc-44+PiW2SWg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Apr 30, 2019 at 5:16 PM Melanie Plageman
<melanieplageman(at)gmail(dot)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).
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fabien COELHO | 2019-05-01 01:53:41 | Re: performance regression when filling in a table |
| Previous Message | Andres Freund | 2019-05-01 01:36:38 | Re: REINDEX INDEX results in a crash for an index of pg_class since 9.6 |