| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
| Cc: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Buildfarm failures for hash indexes: buffer leaks |
| Date: | 2018-11-01 18:04:43 |
| Message-ID: | 20181101180443.fqnoldtka2dq5axz@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2018-10-27 08:18:12 +0200, Fabien COELHO wrote:
>
> Hello Jeff,
>
> > > I suspect the easiest thing to narrow it down would be to bisect the
> > > problem in gcc :(
> >
> > Their commit r265241 is what broke the PostgreSQL build. It also broke the
> > compiler itself--at that commit it was no longer possible to build itself.
> > I had to --disable-bootstrap in order to get a r265241 compiler to test
> > PostgreSQL on.
>
> It seems they have done a API change around some kind of "range" analysis,
> which must have been incomplete.
>
> > Their commit r265375 fixed the ability to compile itself, but built
> > PostgreSQL binaries remain broken there and thereafter.
> >
> > |...]
>
> Thanks a lot for this investigation! I can fill in a gcc bug report. There
> would be a enormous work to narrow it down to a small test case, it is
> unclear how they can act about it, but at least they would know.
Have you done so? If so, what's the bug number?
Greetings,
Andres Freund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tomas Vondra | 2018-11-01 18:33:39 | Re: Parallel threads in query |
| Previous Message | Andres Freund | 2018-11-01 17:54:23 | Re: replication_slots usability issue |