Re: segfault in geqo on experimental gcc animal
От | Martin Liška |
---|---|
Тема | Re: segfault in geqo on experimental gcc animal |
Дата | |
Msg-id | CAObPJ3MF7ZHt1HZE0-hvvJBZR431Kdcrw3OOKq0uswvVoX6yiA@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: segfault in geqo on experimental gcc animal (Fabien COELHO <coelho@cri.ensmp.fr>) |
Ответы |
Re: segfault in geqo on experimental gcc animal
|
Список | pgsql-hackers |
Yes, after the revision I see other failing tests like: ... select_having ... ok 16 ms subselect ... FAILED 92 ms union ... FAILED 77 ms case ... ok 32 ms join ... FAILED 239 ms aggregates ... FAILED 136 ms transactions ... ok 59 ms ... I'm going to investigate that and will inform you guys. Martin On Fri, 15 Nov 2019 at 11:56, Fabien COELHO <coelho@cri.ensmp.fr> wrote: > > > > Yep, I build periodically PostgreSQL package in openSUSE with the latest > > GCC and so that I identified that and isolated to a simple test-case. I > > would expect a fix today or tomorrow. > > Indeed, the gcc issue reported seems fixed by gcc r278259. I'm updating > moonjelly gcc to check if this solves pg compilation woes. > > -- > Fabien.
В списке pgsql-hackers по дате отправления: