From: | Tatsuo Ishii <ishii(at)postgresql(dot)org> |
---|---|
To: | peter_e(at)gmx(dot)net |
Cc: | tgl(at)sss(dot)pgh(dot)pa(dot)us, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: 64-bit API for large object |
Date: | 2012-08-23 00:36:53 |
Message-ID: | 20120823.093653.636172297735617452.t-ishii@sraoss.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> On Wed, 2012-08-22 at 01:14 -0400, Tom Lane wrote:
>> Peter Eisentraut <peter_e(at)gmx(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2012-08-23 00:50:02 | Re: larger shared buffers slows down cluster |
Previous Message | Tom Lane | 2012-08-22 21:58:33 | pgsql: Make a cut at a major-features list for 9.2. |