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/ ---------------------------(end of broadcast)--------------------------- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
