Re: 64-bit API for large object

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

From: Tom Lane <tgl@sss.pgh.pa.us>
To: Tatsuo Ishii <ishii@postgresql.org>
Cc: pgsql-hackers@postgresql.org
Date: 2012-08-27T01:28:03Z
Lists: pgsql-hackers
Tatsuo Ishii <ishii@postgresql.org> writes:
> Here are the list of functions think we need to change.

> 1) Frontend lo_* libpq functions(fe-lobj.c)

> lo_initialize() need to get backend 64-bit large object handling
> function's oid, namely lo_lseek64, lo_tell64, lo_truncate64, loread64,
> lowrite64(explained later). If they are not available, use older
> 32-bit backend functions.

I don't particularly see a need for loread64 or lowrite64.  Who's going
to be reading or writing more than 2GB at once?  If someone tries,
they'd be well advised to reconsider their code design anyway.

			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