. Is it really
needed
change? All its usage is to store the result of len % LOBLKSIZE.
Fixed and back to int32.
Thanks,
2012/9/24 Nozomi Anzai an...@sraoss.co.jp:
Here is 64-bit API for large object version 2 patch.
I checked this patch. It can be applied onto the latest master branch
to use up to 4TB large objects(or 16TB if BLCKSZ changed to
32KB). The patch is based on Jeremy Drake's patch posted on September
23, 2005
(http://archives.postgresql.org/pgsql-hackers/2005-09/msg01026.php)
and reasonably updated/edited to adopt PostgreSQL 9.3 by Nozomi Anzai
for the backend
3) Backend inv_api.c functions(Nozomi Anzai)
No need to add new functions. Just extend them to handle 64-bit data.
BTW , what will happen if older 32-bit libpq accesses large objects
over 2GB?
lo_read and lo_write: they can read or write lobjs using 32-bit API as
long
