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

From Robert Haas
Subject Re: 64-bit API for large object
Date
Msg-id CA+Tgmoa-VXU4OATs2cDsaWf2n_tTxLbXhT9Orpo1_8Hz+2G=Ng@mail.gmail.com
Whole thread Raw
In response to Re: 64-bit API for large object  (Tatsuo Ishii <ishii@postgresql.org>)
List pgsql-hackers
On Tue, Aug 28, 2012 at 10:51 PM, Tatsuo Ishii <ishii@postgresql.org> wrote:
>> 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.

...for anybody!

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Incorrect behaviour when using a GiST index on points
Next
From: Bruce Momjian
Date:
Subject: Re: [BUGS] BUG #6572: The example of SPI_execute is bogus