| From: | Kenneth Marshall <ktm(at)it(dot)is(dot)rice(dot)edu> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | chriskl(at)familyhealth(dot)com(dot)au, chris(at)travelamericas(dot)co, merlin(dot)moncure(at)rcsonline(dot)com, decibel(at)decibel(dot)org, pgsql-advocacy(at)postgresql(dot)org, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: [pgsql-advocacy] MySQL to PostgreSQL, was ENUM type |
| Date: | 2005-07-28 15:04:50 |
| Message-ID: | 20050728150449.GC23645@it.is.rice.edu |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-advocacy pgsql-general |
On Thu, Jul 28, 2005 at 12:53:07AM -0400, Tom Lane wrote:
> Gregory Youngblood <pgcluster(at)netio(dot)org> 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2005-07-28 21:51:28 | Re: MySQL to PostgreSQL, was ENUM type |
| Previous Message | David Fetter | 2005-07-28 07:55:56 | Re: MySQL to PostgreSQL, was ENUM type |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | germ germ | 2005-07-28 15:09:56 | Re: problem inserting with sequence |
| Previous Message | Tom Lane | 2005-07-28 14:47:08 | Re: problem inserting with sequence |