Re: "ERROR: latch already owned" on gharial
От | Noah Misch |
---|---|
Тема | Re: "ERROR: latch already owned" on gharial |
Дата | |
Msg-id | 20220525064658.GA3123194@rfd.leadboat.com обсуждение исходный текст |
Ответ на | Re: "ERROR: latch already owned" on gharial (Andres Freund <andres@anarazel.de>) |
Ответы |
Re: "ERROR: latch already owned" on gharial
|
Список | pgsql-hackers |
On Tue, May 24, 2022 at 06:24:39PM -0700, Andres Freund wrote: > On 2022-05-25 12:45:21 +1200, Thomas Munro wrote: > > Just BTW, that animal has shown signs of a flaky toolchain before[1]. > > I know we have quite a lot of museum exhibits in the 'farm, in terms > > of hardare, OS, and tool chain. In some cases, they're probably just > > forgotten/not on anyone's upgrade radar. If they've shown signs of > > misbehaving, maybe it's time to figure out if they can be upgraded? > > For example, it'd be nice to be able to rule out problems in GCC 4.6.0 > > (that's like running PostgreSQL 9.1.0, in terms of vintage, > > unsupported status, and long list of missing bugfixes from the time > > when it was supported). > > Yea. gcc 4.6.0 is pretty ridiculous - the only thing we gain by testing with a > .0 compiler of that vintage is pain. Could it be upgraded? +1, this is at least the third non-obvious miscompilation from gharial. Installing the latest GCC that builds easily (perhaps GCC 10.3) would make this a good buildfarm member again. If that won't happen, at least add a note to the animal like described in https://postgr.es/m/20211109144021.GD940092@rfd.leadboat.com
В списке pgsql-hackers по дате отправления: