Re: [PATCH] Identify LWLocks in tracepoints
От
Andres Freund
Тема
Re: [PATCH] Identify LWLocks in tracepoints
Дата
Msg-id
20210511173542.ur7dm2yheduhgzdb@alap3.anarazel.de
Ответ на
Re: [PATCH] Identify LWLocks in tracepoints (Andres Freund)
Список
Дерево обсуждения
[PATCH] Identify LWLocks in tracepoints Craig Ringer <craig.ringer@enterprisedb.com>
Re: [PATCH] Identify LWLocks in tracepoints Dmitry Dolgov <9erthalion6@gmail.com>
Re: [PATCH] Identify LWLocks in tracepoints Craig Ringer <craig.ringer@enterprisedb.com>
Re: [PATCH] Identify LWLocks in tracepoints Peter Eisentraut <peter.eisentraut@enterprisedb.com>
Re: [PATCH] Identify LWLocks in tracepoints Craig Ringer <craig.ringer@enterprisedb.com>
Re: [PATCH] Identify LWLocks in tracepoints Peter Eisentraut <peter.eisentraut@enterprisedb.com>
Re: [PATCH] Identify LWLocks in tracepoints Masahiko Sawada <sawada.mshk@gmail.com>
Re: [PATCH] Identify LWLocks in tracepoints Craig Ringer <craig.ringer@enterprisedb.com>
Re: [PATCH] Identify LWLocks in tracepoints Craig Ringer <craig.ringer@enterprisedb.com>
Hi, On 2021-05-10 09:46:02 -0700, Andres Freund wrote: > No worries - I knew that I'd have to do this at some point, even though > I hadn't planned to do that today... I should have all of them green > before end of today. > > I found that I actually can build LLVM 3.9 directly, as clang-6 can > still build it directly (wheras the oldest gcc still installed can't > build it directly). So it's a bit less painful than I thought at first > > The 3.9 instances (phycodurus, dragonet) tests are running right now, > and I'm fairly sure they'll pass (most of a --noreport --nostatus run > passed). Going forward building LLVM 4,5,6 now - the later versions take > longer... Looks like it's all clear now. All but the results for 11 had cleared up until yesterday evening, and the rest came in ok over night. Greetings, Andres Freund
В списке pgsql-hackers по дате отправления
От: Alvaro Herrera
Дата: