| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Back branches vs. gcc 4.8.0 |
| Date: | 2013-04-07 01:11:06 |
| Message-ID: | CA+TgmoYSjNxhDPc5SzxwJGPkpO_o7LGDKxz+RQcQ8xah0LGfoQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Apr 5, 2013 at 9:45 PM, Peter Eisentraut <peter_e(at)gmx(dot)net> wrote:
> So I think this is not a compiler bug or an arms race. We just need to
> fix the code. So I'm in favor of backporting.
I can certainly see this argument. I understand Tom's point about an
arms race, but back-porting this doesn't feel terribly risky to me.
The thing is, if the arms race is escalating faster than we're
comfortable with, we can always opt opt at a later time; it's not as
if back-porting this fix now commits us irrevocably.
Then, too, I tend to think this is more our fault than gcc's - for a change.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rodrigo Barboza | 2013-04-07 01:39:54 | Re: Unrecognized type error (postgres 9.1.4) |
| Previous Message | Amit Kapila | 2013-04-07 00:53:48 | Re: Unrecognized type error (postgres 9.1.4) |