Re: signed vs. unsigned in plpy_procedure.c

From: Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>
To: Andres Freund <andres(at)2ndquadrant(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: signed vs. unsigned in plpy_procedure.c
Date: 2013-07-02 14:54:24
Message-ID: 51D2E9A0.6000201@vmware.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 02.07.2013 13:39, Andres Freund wrote:
> src/postgresql/src/pl/plpython/plpy_procedure.c: In function ‘PLy_procedure_munge_source’:
> src/postgresql/src/pl/plpython/plpy_procedure.c:507:2: warning: comparison of unsigned expression>= 0 is always true [-Wtype-limits]
> Assert(plen>= 0&& plen< mlen);
>
> Which has a point, we assign sprintf()s result to a size_t and then
> check for a negative value. Which doesn't work.
>
> Obviously the impact is miniscule, but removing legitimate warnings is a
> good thing. Trivial patch attached.

Thanks, applied.

- Heikki

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2013-07-02 14:56:38 Re: refresh materialized view concurrently
Previous Message Bruce Momjian 2013-07-02 14:44:53 Re: [9.4 CF 1] The Commitfest Slacker List