On 9/28/12 10:35 AM, Alvaro Herrera wrote:
> Now there is one more problem in this area which is that the patch
> defined a new type pg_int64 for frontend code (postgres_ext.h).  This
> seems a bad idea to me.  We already have int64 defined in c.h.  Should
> we expose int64 to postgres_ext.h somehow?  Should we use standard-
> mandated int64_t instead?  One way would be to have a new configure
> check for int64_t, and if that type doesn't exist, then just don't
> provide the 64 bit functionality to frontend.

Or create a new type like pg_lo_off_t.

In response to

• Re: 64-bit API for large object at 2012-09-28 14:35:55 from Alvaro Herrera

pgsql-hackers by date

Next:	From: Merlin Moncure	Date: 2012-10-01 13:05:18
	Subject: Re: CTE optimization fence on the todo list?
Previous:	From: Peter Geoghegan	Date: 2012-10-01 11:33:07
	Subject: Re: Hash id in pg_stat_statements