Re: Adding a test for speculative insert abort case

From: Melanie Plageman <melanieplageman(at)gmail(dot)com>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Ashwin Agrawal <aagrawal(at)pivotal(dot)io>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>, Peter Geoghegan <pg(at)bowt(dot)ie>, Taylor Vesely <tvesely(at)pivotal(dot)io>
Subject: Re: Adding a test for speculative insert abort case
Date: 2020-02-12 01:20:05
Message-ID: CAAKRu_aaBZy=2jd_9SuVQts0FTx6dXCXVPKUqjd7reWn7icoxg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Feb 11, 2020 at 4:45 PM Andres Freund <andres(at)anarazel(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Masahiko Sawada 2020-02-12 02:05:48 Re: [HACKERS] Moving relation extension locks out of heavyweight lock manager
Previous Message Melanie Plageman 2020-02-12 00:57:05 Re: Avoiding hash join batch explosions with extreme skew and weird stats