Horton
Menu

Re: 64-bit API for large object

Tom Lane <tgl@sss.pgh.pa.us>

View thread
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Tatsuo Ishii <ishii@postgresql.org>
Cc: kaigai@kaigai.gr.jp, pgsql-hackers@postgresql.org, anzai@sraoss.co.jp, nagata@sraoss.co.jp
Date: 2012-09-21T03:33:03Z
Lists: pgsql-hackers 
Tatsuo Ishii <ishii@postgresql.org> writes:
> To pass 64-bit integer to PQfn, PQArgBlock is used like this: int *ptr
> is a pointer to 64-bit integer and actual data is placed somewhere
> else.

Yeah, I think we have to do it like that.  Changing the size of
PQArgBlock would be a libpq ABI break, which IMO is sufficiently painful
to kill this whole proposal.  Much better a little localized ugliness
in fe-lobj.c.

			regards, tom lane

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Remove all the special-case code for INT64_IS_BUSTED, per decision that