| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Cc: | Jeremy Drake <pgsql(at)jdrake(dot)com>, Tom Lane <tgl(at)postgresql(dot)org> |
| Subject: | Re: Re: [COMMITTERS] pgsql: GIN index build's allocatedMemory counter needs to be long, not |
| Date: | 2007-11-18 20:46:40 |
| Message-ID: | 200711182146.43503.peter_e@gmx.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
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/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-11-18 20:57:59 | Re: Re: [COMMITTERS] pgsql: GIN index build's allocatedMemory counter needs to be long, not |
| Previous Message | Jeremy Drake | 2007-11-18 20:36:54 | Re: [COMMITTERS] pgsql: GIN index build's allocatedMemory counter needs to be long, not |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-11-18 20:57:59 | Re: Re: [COMMITTERS] pgsql: GIN index build's allocatedMemory counter needs to be long, not |
| Previous Message | Jeremy Drake | 2007-11-18 20:36:54 | Re: [COMMITTERS] pgsql: GIN index build's allocatedMemory counter needs to be long, not |