Re: 64-bit API for large object
Tatsuo Ishii <ishii@postgresql.org>
From: Tatsuo Ishii <ishii@postgresql.org>
To: peter_e@gmx.net
Cc: tgl@sss.pgh.pa.us, pgsql-hackers@postgresql.org
Date: 2012-08-23T00:36:53Z
Lists: pgsql-hackers
> On Wed, 2012-08-22 at 01:14 -0400, Tom Lane wrote: >> Peter Eisentraut <peter_e@gmx.net> writes: >> > On Wed, 2012-08-22 at 07:27 +0900, Tatsuo Ishii wrote: >> >> I found this in the TODO list: >> >> Add API for 64-bit large object access >> >> If this is a still valid TODO item and nobody is working on this, I >> >> would like to work in this. >> >> > Large objects are limited to 2 GB in size, so a 64-bit API doesn't sound >> > very useful to me at the moment. >> >> Not entirely. pg_largeobject.pageno is int32, but that's still 2G pages >> not bytes, so there's three or so orders of magnitude that could be >> gotten by expanding the client-side API before we'd have to change the >> server's on-disk representation. > > Well then a 64-bit API would be very useful. Go for it. :-) Ok, I will do it. -- 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