| From: | Yury Zhuravlev <u(dot)zhuravlev(at)postgrespro(dot)ru> |
|---|---|
| To: | <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Crash with old Windows on new CPU |
| Date: | 2016-02-13 19:28:19 |
| Message-ID: | 2bb41f8c-ba52-4f53-addd-0e173c72671a@postgrespro.ru |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane wrote:
> Lastly, I'd like to see some discussion of what side effects
> "_set_FMA3_enable(0);" has ... I rather doubt that it's really
> a magic-elixir-against-crashes-with-no-downsides. That would
> give us some context to estimate the risks of this code executing
> when it's not really needed. Without that, I'd be worried that
> this cure is worse than the disease because it breaks cases that
> weren't broken befor
I think I have already proposed to drop MSVC support? :)
Too many problems due to of one compiler...
PS Cry from the heart. I work too much with him. Never mind.
--
Yury Zhuravlev
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christian Ullrich | 2016-02-13 22:09:28 | Re: Crash with old Windows on new CPU |
| Previous Message | Tom Lane | 2016-02-13 18:32:01 | Re: pgsql: Introduce group locking to prevent parallel processes from deadl |