From: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
---|---|
To: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
Cc: | Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Japin Li <japinli(at)hotmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Cannot find a working 64-bit integer type on Illumos |
Date: | 2024-12-03 13:22:56 |
Message-ID: | 6b1edd7b-0c56-485b-8788-7567f1523f0f@eisentraut.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 29.11.24 20:30, Thomas Munro wrote:
> On Fri, Nov 29, 2024 at 11:12 PM Thomas Munro <thomas(dot)munro(at)gmail(dot)com> wrote:
> I was thinking about that ECPG stuff: I bet real applications prefer
> to use int64_t etc directly too instead of long, the worst type in C.
> I wondered if the embedded SQL standard might know about that these
> days (ECPGt_int64_t?), but I don't have the standard to hand. DB2's
> embedded SQL seems to have a type sqlint64, but I didn't look too
> closely and of course even if we wanted to do something like that as
> an optional API option, that'd be a later change.
Interesting:
i) If “long long” is specified, then the <host parameter data type> of
HV is BIGINT.
ii) If “long” is specified, then the <host parameter data type> of HV is
INTEGER.
iii) If “short” is specified, then the <host parameter data type> of HV
is SMALLINT.
[...]
I suppose that makes sense.
> BTW I forgot to mention earlier, I peeked at the source of gettext on
> NetBSD and illumos, and both appear to handle those special
> <inttypes.h> tokens when loading message catalogues.
Ah great, thanks for checking that.
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2024-12-03 13:24:47 | Re: Cannot find a working 64-bit integer type on Illumos |
Previous Message | Peter Eisentraut | 2024-12-03 12:59:02 | Re: NOT ENFORCED constraint feature |