On 1/15/13 6:36 AM, Andres Freund wrote:
> I just think that the price of fixing a single Assert() that hasn't
> changed in years where the variable isn't likely to ever get signed is
Well, once you get past that one change you proposed, you will also find
pg_standby.c: In function 'SetWALFileNameForCleanup':
pg_standby.c:348:3: error: comparison of unsigned expression >= 0 is
always true [-Werror=type-limits]
(which, curiously, is the only one that clang complains about).
I don't like removing safety checks from code when there is no other
mechanism that could make up for it somehow.
I think the best practice at the moment, as with most gcc -Wextra
warnings, is to manually check them once in a while.
In response to
pgsql-hackers by date
|Next:||From: Claudio Freire||Date: 2013-01-16 15:23:14|
|Subject: Re: Parallel query execution|
|Previous:||From: Simon Riggs||Date: 2013-01-16 15:08:33|
|Subject: Re: log_lock_waits to identify transaction's relation|