Resent-From: POSTGRES mailing list <postman@postgres.Berkeley.EDU>
Resent-Message-Id: <199611130951.BAA14292@nobozo.CS.Berkeley.EDU>
Sender: owner-postman@postgres.Berkeley.EDU
Message-Id: <199611130951.KAA12527@grizzly.genua.de>
To: postgres@postgres.Berkeley.EDU
cc: harlan@GeNUA.DE
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 13 Nov 1996 10:51:29 +0100
From: Magnus Harlander <Magnus_Harlander@GeNUA.DE>
Resent-To: postgres-redist@postgres.Berkeley.EDU
Resent-Date: Wed, 13 Nov 96 01:51:54 -0800
Resent-XMts: smtp

Hi,

I've made a small modification to the large object code and wanted just to
make sure I've not violated any deeply buried rules.

We are setting up a postgres app with a large number of large objects.
Since los are stored in tables and a separate table is allocated for
each lo the data/base/dbname dir would grow immensely. I've added 100
subdirs 00-99 and renamed the Xinv and Xinx to NN/v and NN/x (makes also
4 letters). The dirname is determined by OID % 100. 
As far as I can see it seems to work. I've already loaded around  10000 
los and still can access them. 
Are there any comments about that, and is anybody interested in the patches
for use in future releases (this works for pg95-1.00 and pg95-1.05).

\Magnus

btw. I have also a perl5 PG.pm which can handle large objects.


==============================================================================
   To add/remove yourself to/from the POSTGRES mailing list: send mail with 
   the subject line ADD or DEL to "postgres-request@postgres.Berkeley.EDU".
   If this fails, send mail to "post_questions@postgres.Berkeley.EDU" and
   a human will deal with it.  DO NOT post to the "postgres" mailing list.
==============================================================================
              URL: http://s2k-ftp.CS.Berkeley.EDU:8000/postgres/