On Thu, Jul 28, 2005 at 12:53:07AM -0400, Tom Lane wrote:
> Gregory Youngblood <[EMAIL PROTECTED]> writes:
> > ... the problem is unsigned bigint in mysql to postgresql.
> > There's not another larger integer size that can be used that would
> > allow the 18446744073709551615 (is that the max value?) max value
> > available in mysql. Or am I missing something?
>
> You'd have to translate that to NUMERIC, which would work but would
> take a bit of a performance hit ...
>
> regards, tom lane
>
Since the numeric range of the PostgreSQL bigint and the MySQL
unsigned bigint is the same, just shifted. How difficult would it
be to put a bigint overlay in PostgreSQL that would do that for
you. We had to do this on the application side to make use of the
PostgreSQL bigint and not the slower NUMERIC.
Ken
---------------------------(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
