Re: pgsql: Better fix for determining minimum and maximum int64 values that

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: pgsql-committers(at)postgresql(dot)org, pgsql-hackers(at)postgresql(dot)org
Subject: Re: pgsql: Better fix for determining minimum and maximum int64 values that
Date: 2007-02-18 16:58:24
Message-ID: 200702181758.25032.peter_e@gmx.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

Alvaro Herrera wrote:
> Peter Eisentraut wrote:
> > Log Message:
> > -----------
> > Better fix for determining minimum and maximum int64 values that
> > doesn't require stdint.h and works for "busted" int64.
>
> Nice trick -- is this worth being in c.h or thereabouts?

I was thinking about adding something like PG_INT64_MAX etc. to c.h, but
that might have required adding limit.h to c.h and perhaps other
rearrangements, and that would have gone too far for the moment. If
more call sites use it, it should be refactored.

--
Peter Eisentraut
http://developer.postgresql.org/~petere/

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2007-02-18 19:49:25 pgsql: Fix portal management code to support non-default command
Previous Message User Okbob 2007-02-18 12:22:33 plpsm - plpgpsm: enhanced diagnostics for warnings

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2007-02-18 17:32:41 Re: patch adding new regexp functions
Previous Message Knut P. Lehre 2007-02-18 16:21:02 FETCH from scroll cursor does not return count in libpq PQcmdStatus