| From: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
|---|---|
| To: | Melanie Plageman <melanieplageman(at)gmail(dot)com> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, 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-03-24 12:33:57 |
| Message-ID: | CAA4eK1Lkf3CtjHPiKv8gNLNF-5OoQ_=5GVVM1pRv-8P6g5TxAw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Feb 12, 2020 at 6:50 AM Melanie Plageman
<melanieplageman(at)gmail(dot)com> wrote:
>
>
> 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!
>
Can we change the status of CF entry for this patch [1] to committed
or is there any work pending?
[1] - https://commitfest.postgresql.org/27/2200/
--
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2020-03-24 12:38:29 | Re: Improve checking for pg_index.xmin |
| Previous Message | Peter Eisentraut | 2020-03-24 10:34:55 | Re: Silence compiler warnings with Python 3.9 |