Re: Adding a test for speculative insert abort case
| От | Amit Kapila |
|---|---|
| Тема | Re: Adding a test for speculative insert abort case |
| Дата | |
| Msg-id | CAA4eK1Lkf3CtjHPiKv8gNLNF-5OoQ_=5GVVM1pRv-8P6g5TxAw@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Adding a test for speculative insert abort case (Melanie Plageman <melanieplageman@gmail.com>) |
| Ответы |
Re: Adding a test for speculative insert abort case
|
| Список | pgsql-hackers |
On Wed, Feb 12, 2020 at 6:50 AM Melanie Plageman <melanieplageman@gmail.com> wrote: > > > On Tue, Feb 11, 2020 at 4:45 PM Andres Freund <andres@anarazel.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
В списке pgsql-hackers по дате отправления: