Re: Keep elog(ERROR) and ereport(ERROR) calls in the cold path
От | Tom Lane |
---|---|
Тема | Re: Keep elog(ERROR) and ereport(ERROR) calls in the cold path |
Дата | |
Msg-id | 389276.1606267703@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: Keep elog(ERROR) and ereport(ERROR) calls in the cold path (Alvaro Herrera <alvherre@alvh.no-ip.org>) |
Ответы |
Re: Keep elog(ERROR) and ereport(ERROR) calls in the cold path
|
Список | pgsql-hackers |
Alvaro Herrera <alvherre@alvh.no-ip.org> writes: >> On Wed, 25 Nov 2020 at 04:55, Tom Lane <tgl@sss.pgh.pa.us> wrote: >>> walleye's been failing since this patchset went in: >>> I have no idea what to make of that, but it looks more like a compiler bug >>> than anything else. > Apparently the bug was fixed days after it was reported, > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86048 > but they haven't made a release containing the fix yet. Wait ... the second part of that doesn't seem to be true. According to http://mingw-w64.org/doku.php/versions mingw-w64 has made at least three releases since this bug was fixed. Surely they're shipping something newer than 8.1.0 by now. So maybe, rather than hacking up the attribute stuff for a bug that might bite us again anyway in future, we ought to press walleye's owner to install a more recent compiler. regards, tom lane
В списке pgsql-hackers по дате отправления: