| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>, Andrew Dunstan <andrew(at)dunslane(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Dave Page <dpage(at)pgadmin(dot)org> |
| Subject: | Re: problems on Solaris |
| Date: | 2015-06-24 17:10:12 |
| Message-ID: | CA+TgmoZMb6NzR-_UsoFFwZgm2xxrJUWk5wCgZwUjnnfnqk=8tQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Jun 24, 2015 at 8:42 AM, Andres Freund <andres(at)anarazel(dot)de> wrote:
> I'm wondering wether we should add a #warning to atomic.c if either the
> fallback memory or compiler barrier is used? Might be annoying to people
> using -Werror, but I doubt that's possible anyway on such old systems.
#warning isn't totally portable, so I think it might be better not to
do that. Yeah, it'll work in a lot of places, but the sorts of
obscure systems where the fallbacks are used are also more likely to
have funky compilers that just barf on the directive outright.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fabrízio de Royes Mello | 2015-06-24 17:12:18 | Re: Add CINE for ALTER TABLE ... ADD COLUMN |
| Previous Message | Simon Riggs | 2015-06-24 17:02:09 | Re: Multixid hindsight design |