Postgres Pro
Downloads
Home   >   mailing lists

Re: Re: [COMMITTERS] pgsql: GIN index build's allocatedMemory counter needs to be long, not - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: Re: [COMMITTERS] pgsql: GIN index build's allocatedMemory counter needs to be long, not
Date
Msg-id 200711182146.43503.peter_e@gmx.net
Whole thread Raw
In response to Re: [COMMITTERS] pgsql: GIN index build's allocatedMemory counter needs to be long, not  (Jeremy Drake <pgsql@jdrake.com>)
Responses Re: Re: [COMMITTERS] pgsql: GIN index build's allocatedMemory counter needs to be long, not  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tree view 
Jeremy Drake wrote:
> I don't know if this has been discussed before, but you are aware that it
> is not dictated by the C standard that sizeof(long) == sizeof(void*)?

As evidenced by this piece of code in postgres.h:

typedef unsigned long Datum;    /* XXX sizeof(long) >= sizeof(void *) */

> The best counter-example I know is Windows x64, where sizeof(long) == 4
> while sizeof(void*) == 8.

Yes, and there is lots of work left to do to support that.

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

pgsql-hackers by date:

Previous
From: Jeremy Drake
Date:
Subject: Re: [COMMITTERS] pgsql: GIN index build's allocatedMemory counter needs to be long, not
Next
From: Tom Lane
Date:
Subject: Re: Re: [COMMITTERS] pgsql: GIN index build's allocatedMemory counter needs to be long, not