From: | Zoltan Boszormenyi <zb(at)cybertec(dot)at> |
---|---|
To: | pgsql-patches(at)postgresql(dot)org |
Cc: | Hans-Juergen Schoenig <hs(at)cybertec(dot)at> |
Subject: | Fix HAVE_LONG[_LONG]_INT_64 to really define to 1 |
Date: | 2008-03-11 10:39:06 |
Message-ID: | 47D6614A.5090905@cybertec.at |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-patches |
Hi,
I am working on this TODO item:
* Consider allowing 64-bit integers and floats to be passed by value on
64-bit platforms
Also change 32-bit floats (float4) to be passed by value at the same
time.
For genbki.sh, to correctly determine whether HAVE_LONG_INT_64
is defined, the attached bugfix is needed in the configure.in machinery.
This way the pg_config.h actually conforms to the comments for
HAVE_LONG_INT_64 and HAVE_LONG_LONG_INT_64.
Best regards,
Zoltán Böszörményi
--
----------------------------------
Zoltán Böszörményi
Cybertec Schönig & Schönig GmbH
http://www.postgresql.at/
Attachment | Content-Type | Size |
---|---|---|
fix-64-bit-long-int-defines.patch | text/x-patch | 1.6 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Heikki Linnakangas | 2008-03-11 12:34:07 | Re: [PERFORM] Very slow (2 tuples/second) sequential scan after bulk insert; speed returns to ~500 tuples/second after commit |
Previous Message | Heikki Linnakangas | 2008-03-11 10:25:18 | Re: CopyReadLineText optimization |