From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Josh Berkus <josh(at)agliodbs(dot)com> |
Cc: | Andreas Seltenreich <andreas(dot)seltenreich(at)credativ(dot)de>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com>, Christoph Berg <christoph(dot)berg(at)credativ(dot)de>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>, Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>, Bernd Helmle <bernd(at)oopsware(dot)de> |
Subject: | Re: 9.3.9 and pg_multixact corruption |
Date: | 2015-09-28 18:37:58 |
Message-ID: | CA+TgmoZPgQZ6EfubBx7NUbkLSzjf_kZ7_u88G-4=J3R9s8Y+xQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Sep 28, 2015 at 2:34 PM, Josh Berkus <josh(at)agliodbs(dot)com> wrote:
> On 09/28/2015 08:10 AM, Robert Haas wrote:
>> -1 on that idea. I really don't think that we should categorically
>> decide we don't support higher optimization levels. If the compiler
>> has a bug, then the compiler manufacturer should fix it, and it's not
>> our fault. If the compiler doesn't have a bug and our stuff is
>> blowing up, then we have a bug and should fix it. I suppose there
>> could be some grey area but hopefully not too much.
>
> Or it's PILBChAK. I know Sun-CC used to warn that -O3 was unsuitable for
> most programs because it could change behavior.
I'm attempting to decipher this acronym. Problem is located between
chair and keyboard? But I don't see how that applies here.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Stephen Frost | 2015-09-28 19:03:51 | Re: RLS open items are vague and unactionable |
Previous Message | Josh Berkus | 2015-09-28 18:34:29 | Re: 9.3.9 and pg_multixact corruption |