From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | Richard Emberson <emberson(at)phc(dot)net>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Large Object Location in 7.3 |
Date: | 2002-03-25 07:55:50 |
Message-ID: | 17524.1017042950@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> Richard Emberson wrote:
>> I expect (actually hope) to have thousands and thousands of blob/clobs
>> in the db I am designing.
>> I would like such largeobjects to be stored in their own file system.
> Sure, find the oid of pg_largeobject and symlink that to another file
> system. You need to do that toast table and any indexes for the table
> too.
If Richard's envisioning more than 1GB of large objects, I don't think
he's going to be very satisfied with manual symlinking.
This does bring up an interesting point: the tablespace schemes we've
discussed so far don't allow system catalogs to be moved out of the
default tablespace for a database. That doesn't bother me for most
of the system catalogs ... but pg_largeobject seems like it might be
an exception.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | tony | 2002-03-25 08:02:14 | Register article |
Previous Message | Tom Lane | 2002-03-25 07:49:22 | Re: Another notify question |