From: | Uncle George <gatgul(at)voicenet(dot)com> |
---|---|
To: | pgsql-ports(at)postgreSQL(dot)org |
Subject: | RH60+ALPHA + >2gig filesizes |
Date: | 1999-08-02 19:25:24 |
Message-ID: | 37A5F0A4.14040865@voicenet.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-ports |
Using ( or trying to ) the JDBC interface, one finds the my porting
effort is just not complete enough.
Postgres seems to like 2^32-1 byte/file as a rule. On the ALPHA there
is the ability to go beyond 2^32-1 bytes ( in theory ~17gb, due to
limitations of the ext2 filesystem ). u do not get an EOF/error at the
(32bit) 2gig intel file limit.
And What of loread/lowrite(loseek/lotell) ? it is theoretical to give a
len >2gig ( but the mem/architecture is just not there yet for mem that
large ). Are offsets passed back to the JDBC/client as 32bit ints?
Can any of ur DB file architectures handle the >32bit offsets? If so how
far? ( ie ext2 is limited to 17gig ).
Where are u folks going with this "offset" inconsistency?
gat
From | Date | Subject | |
---|---|---|---|
Next Message | Uncle George | 1999-08-02 21:48:15 | [Fwd: RH60+ALPHA + >2gig filesizes] |
Previous Message | Mario Cerna | 1999-08-02 15:52:57 | A probelm |