From: | Magnus Hagander <magnus(at)hagander(dot)net> |
---|---|
To: | Bruce Momjian <bruce(at)momjian(dot)us> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Peter Eisentraut <peter_e(at)gmx(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: ssize_t vs win64 |
Date: | 2010-01-03 00:03:51 |
Message-ID: | 9837222c1001021603m7fcb928cud3077b93d392d1a5@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sun, Jan 3, 2010 at 01:01, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> Tom Lane wrote:
>> Bruce Momjian <bruce(at)momjian(dot)us> writes:
>> > Tom Lane wrote:
>> >> I think the Python guys are up against the same problem as us, namely
>> >> substituting for the platform's failure to define the type.
>>
>> > I am unclear if accepting what Python chose as a default is the right
>> > route vs. doing more research.
>>
>> What exactly do you think we might do differently? There is only one
>> sane definition for ssize_t on a 64-bit platform.
>
> Well, I saw two definitions listed in this thread, and it wasn't clear
> to me the Python one was known to be the correct one:
>
> PostgreSQL has it as
> typedef long ssize_t;
>
> And python has it as:
> typedef __int64 ssize_t;
You're missing the crucial point: That is that PostgreSQL uses long on
*32-bit*. Python uses __int64 on *64-bit*. PostgreSQL didn't *have* a
definition on 64-bit, so we fell back on the 32-bit one.
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2010-01-03 00:07:49 | Re: ssize_t vs win64 |
Previous Message | Tom Lane | 2010-01-03 00:02:30 | Re: ssize_t vs win64 |