| From: | Martin Liška <marxin(dot)liska(at)gmail(dot)com> |
|---|---|
| To: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: segfault in geqo on experimental gcc animal |
| Date: | 2019-11-15 11:24:49 |
| Message-ID: | CAObPJ3MF7ZHt1HZE0-hvvJBZR431Kdcrw3OOKq0uswvVoX6yiA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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(at)cri(dot)ensmp(dot)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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ranier Vilela | 2019-11-15 11:25:07 | [PATCH][BUG FIX] Unsafe access pointers. |
| Previous Message | Amit Kapila | 2019-11-15 10:49:27 | Re: PATCH: logical_work_mem and logical streaming of large in-progress transactions |