Re: 64-bit API for large object
Tatsuo Ishii <ishii@postgresql.org>
From: Tatsuo Ishii <ishii@postgresql.org>
To: tgl@sss.pgh.pa.us
Cc: pgsql-hackers@postgresql.org
Date: 2012-08-27T01:58:44Z
Lists: pgsql-hackers
>> 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. Ok, loread64 and lowrite64 will not be added. -- Tatsuo Ishii SRA OSS, Inc. Japan English: http://www.sraoss.co.jp/index_en.php Japanese: http://www.sraoss.co.jp
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Remove all the special-case code for INT64_IS_BUSTED, per decision that
- 901be0fad403 9.0.0 cited