Re: 64-bit API for large object - Mailing list pgsql-hackers

From Tatsuo Ishii
Subject Re: 64-bit API for large object
Date
Msg-id 20120829.115120.1064387111964070806.t-ishii@sraoss.co.jp
Whole thread Raw
In response to Re: 64-bit API for large object  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: 64-bit API for large object
List pgsql-hackers
> pg_largeobject.pageno is a signed int, so I don't think we can let it go
> past 2^31-1, so half that.
> 
> We could buy back the other bit if we redefined the column as oid
> instead of int4 (to make it unsigned), but I think that would create
> fairly considerable risk of confusion between the loid and pageno
> columns (loid already being oid).  I'd just as soon not go there,
> at least not till we start seeing actual field complaints about
> 4TB being paltry ;-)

Agreed. 4TB should be enough.
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese: http://www.sraoss.co.jp



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: 64-bit API for large object
Next
From: Robert Haas
Date:
Subject: Re: MySQL search query is not executing in Postgres DB