X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id EFF32D1EA10 for ; Thu, 6 May 2004 06:06:09 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 70988-03 for ; Thu, 6 May 2004 06:05:50 -0300 (ADT) Received: from kieser1.demon.co.uk (unknown [195.166.116.245]) by svr1.postgresql.org (Postfix) with ESMTP id 1F391D1EA74 for ; Thu, 6 May 2004 06:05:48 -0300 (ADT) Received: from kieser.net (localhost.localdomain [127.0.0.1]) by kieser1.demon.co.uk (Postfix) with ESMTP id 3BDEC6971B; Thu, 6 May 2004 06:03:28 -0400 (EDT) Message-ID: <409A0D6D.3040200@kieser.net> Date: Thu, 06 May 2004 10:03:25 +0000 From: Bradley Kieser User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7b) Gecko/20040316 X-Accept-Language: en, en-us MIME-Version: 1.0 To: Matt Clark Cc: pgsql-admin@postgresql.org, emberson@phc.net Subject: Re: Postgres & large objects References: <006f01c43341$73ed9f60$8300a8c0@solent> In-Reply-To: <006f01c43341$73ed9f60$8300a8c0@solent> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at postgresql.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200405/57 X-Sequence-Number: 13373 Matt, Not really the answer that you are looking for and you may already do this, but if it's a disk space or performance issue then I would suggest moving the PGDATA dir (or the location if you are using locations) onto a RAID5 disk array - means you can ramp up the space and you get the performance gains of RAID5, not to mention the safety of a FS that recovers from disk failure! Brad Matt Clark wrote: > Hello all, > > It seems I'm trying to solve the same problem as Richard Emberson had > a while ago (thread here: > http://archives.postgresql.org/pgsql-general/2002-03/msg01199.php). > > Essentially I am storing a large number of large objects in the DB > (potentially tens or hundreds of gigs), and would like the > pg_largeobject table to be stored on a separate FS. But of course > it's not just one file to symlink and then forget about, it's a number > of files that get created. > > So, has anyone come up with a way to get the files for a table created > in a particular place? I know that tablespsaces aren't done yet, but > a kludge will do (or a patch come to that - we're runing redhat's > 7.2.3 RPMs, but could switch if necessary). I had thought that if the > filenames were predictable it might be possible to precreate a bunch > of zero-length files and symlink them in advance... > > Cheers > > Matt > >