From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Christoph Berg <cb(at)df7cb(dot)de>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: gcc5: initdb produces gigabytes of _fsm files |
Date: | 2015-02-13 00:09:37 |
Message-ID: | CA+TgmoZhXVvzD8ijHH-kr-e2+Oi=+kekkmvFR0o7_EZtOp_hbg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Feb 12, 2015 at 6:16 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> I wrote:
>> Christoph Berg <cb(at)df7cb(dot)de> writes:
>>> gcc5 is lurking in Debian experimental, and it's breaking initdb.
>
>> Yeah, I just heard the same about Red Hat as well:
>> https://bugzilla.redhat.com/show_bug.cgi?id=1190978
>> Not clear if it's an outright compiler bug or they've just found some
>> creative new way to make an optimization assumption we're violating.
>
> Apparently, it's the former. See
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1190978#c3
>
> I will be unamused if the gcc boys try to make an argument that they
> did some valid optimization here.
You're new here, aren't you?
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2015-02-13 00:18:11 | Re: pg_basebackup -x/X doesn't play well with archive_mode & wal_keep_segments |
Previous Message | Bo Tian | 2015-02-12 23:46:18 | question on Postgres smart shutdown mode |