Re: Adding a test for speculative insert abort case

From: Andres Freund <andres(at)anarazel(dot)de>
To: pgsql-hackers(at)lists(dot)postgresql(dot)org,Peter Geoghegan <pg(at)bowt(dot)ie>,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 02:09:51
Message-ID: EB208EEB-200D-4BD6-935D-BFD03E71CEB4@anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

On April 30, 2019 6:43:08 PM PDT, Peter Geoghegan <pg(at)bowt(dot)ie> wrote:
>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).

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.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Thomas Munro 2019-05-01 02:13:46 Re: Adding a test for speculative insert abort case
Previous Message Chanon Sajjamanochai 2019-05-01 01:55:50 PostgreSQL Asian language support for full text search using ICU (and also updating pg_trgm)