| From: | Tatsuo Ishii <ishii(at)postgresql(dot)org> |
|---|---|
| To: | tgl(at)sss(dot)pgh(dot)pa(dot)us |
| Cc: | peter_e(at)gmx(dot)net, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: 64-bit API for large object |
| Date: | 2012-08-22 05:20:43 |
| Message-ID: | 20120822.142043.2117276379711762680.t-ishii@sraoss.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
>> 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.
Right. You have already explained that in this:
http://archives.postgresql.org/pgsql-hackers/2010-09/msg01888.php
> There might well be some local variables in the server's largeobject
> code that would need to be widened, but that's the easiest part of the
> job.
--
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 | Vlad Arkhipov | 2012-08-22 07:11:46 | Re: Audit Logs WAS: temporal support patch |
| Previous Message | Tom Lane | 2012-08-22 05:14:06 | Re: 64-bit API for large object |