Re: Unportable coding in reorderbuffer.h

From: Andres Freund <andres(at)2ndquadrant(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Unportable coding in reorderbuffer.h
Date: 2014-03-07 18:38:35
Message-ID: 20140307183835.GB23339@awork2.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2014-03-07 13:27:28 -0500, Tom Lane wrote:
> Andres Freund <andres(at)2ndquadrant(dot)com> writes:
> > A patch fixing this is attached. I've added some more local variables to
> > deal with the longer lines...
>
> Since I've got a compiler in captivity that complains about this,
> I'll take care of checking and committing this patch.

Thanks.

The tests specific for the feature can be run with (cd
contrib/test_decoding && make -s check), as they require non-default
PGC_POSTMASTER settings.

> I still think it might be a good idea to spin up a buildfarm member
> running "gcc -ansi -pedantic", even if we don't see that as a particularly
> useful case in practice. Thoughts?

I tried to compile with both -ansi -pedantic -std=c90 to catch potential
further issues, but at least my gcc version makes the output completely
drown in various warnings. Some can be individually disabled, but lots
of them seem to be only be covered by pretty general warning categories.
-ansi -std=c90 -Wno-variadic-macros works reasonably well tho.

Greetings,

Andres Freund

--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2014-03-07 18:54:42 Re: on_exit_reset fails to clear DSM-related exit actions
Previous Message Robert Haas 2014-03-07 18:38:32 Re: on_exit_reset fails to clear DSM-related exit actions