Re: [COMMITTERS] pgsql: Centralize definition of integer limits.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, pgsql-hackers(at)postgreSQL(dot)org, Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>
Subject: Re: [COMMITTERS] pgsql: Centralize definition of integer limits.
Date: 2015-03-31 16:10:48
Message-ID: 19400.1427818248@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

Andres Freund <andres(at)anarazel(dot)de> writes:
> On 2015-03-30 21:50:09 +0200, Andres Freund wrote:
>> I'm too fried from the redeye back from pgconf nyc to do anything
>> complicated, but it seems quite possible to define int64/uint64 based
>> the stdint.h types if available. And generally a good idea too. I guess
>> I'll try that tomorrow; unless Andrew beats me to it.

> It's possible to do that, but it's not as trivial as I'd hoped. For one
> we'd need to include stdint.h in some places we don't today
> (postgres_ext.h), for another we'd need some uglyness to determine the
> correct printf modifier for int64_t (can't use PRId64 etc afaics).

Yeah, I thought the printf strings would be the sticking point :-(

> I'm tempted to just prefix our limits with PG_ and define them
> unconditionally, including appropriate casts to our types.

I don't have a better idea.

regards, tom lane

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Andres Freund 2015-03-31 16:15:48 Re: [COMMITTERS] pgsql: Centralize definition of integer limits.
Previous Message Bruce Momjian 2015-03-31 15:51:43 pgsql: initdb: remove unnecessary VACUUM FULL

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2015-03-31 16:15:48 Re: [COMMITTERS] pgsql: Centralize definition of integer limits.
Previous Message Bruce Momjian 2015-03-31 15:51:54 Re: double vacuum in initdb