Horton
Menu

Re: 64-bit API for large object

Tatsuo Ishii <ishii@postgresql.org>

View thread
From: Tatsuo Ishii <ishii@postgresql.org>
To: tgl@sss.pgh.pa.us
Cc: pgsql-hackers@postgresql.org
Date: 2012-08-29T02:51:20Z
Lists: 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

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Remove all the special-case code for INT64_IS_BUSTED, per decision that