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 488CBD1EAA2 for ; Thu, 6 May 2004 06:31:12 -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 82262-03 for ; Thu, 6 May 2004 06:30:53 -0300 (ADT) Received: from bayswater1.ymogen.net (host-154-240-27-217.pobox.net.uk [217.27.240.154]) by svr1.postgresql.org (Postfix) with ESMTP id C7E6AD1F224 for ; Thu, 6 May 2004 06:30:50 -0300 (ADT) Received: from solent (82-68-95-1.dsl.in-addr.zen.co.uk [82.68.95.1]) by bayswater1.ymogen.net (Postfix) with ESMTP id 39BBA9C938; Thu, 6 May 2004 10:30:10 +0100 (BST) From: "Matt Clark" To: "'Bradley Kieser'" Cc: , Subject: Re: Postgres & large objects Date: Thu, 6 May 2004 10:31:00 +0100 Message-ID: <008101c4334c$d834da50$8300a8c0@solent> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.6626 In-Reply-To: <409A0D6D.3040200@kieser.net> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Importance: Normal 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/58 X-Sequence-Number: 13374 Thanks, but it's already on a RAID array with a battery backed controller and a journaled FS. The deal is that I don't really want to spend the money on expanding that storage for data that isn't very critical at all. I want to stick these blobs on a cheap bunch of ATA disks basically, as comparing the price of a terabyte of ATA mirrored disks and the same TB on SCSI hardware raid is enlightening.=20=20 M -----Original Message----- From: Bradley Kieser [mailto:brad@kieser.net]=20 Sent: 06 May 2004 11:03 To: Matt Clark Cc: pgsql-admin@postgresql.org; emberson@phc.net Subject: Re: [ADMIN] Postgres & large objects Matt, Not really the answer that you are looking for and you may already do=20 this, but if it's a disk space or performance issue then I would suggest=20 moving the PGDATA dir (or the location if you are using locations) onto=20 a RAID5 disk array - means you can ramp up the space and you get the=20 performance gains of RAID5, not to mention the safety of a FS that=20 recovers from disk failure! Brad Matt Clark wrote: > Hello all, >=20=20 > It seems I'm trying to solve the same problem as Richard Emberson had > a while ago (thread here:=20 > http://archives.postgresql.org/pgsql-general/2002-03/msg01199.php).=20 >=20=20 > Essentially I am storing a large number of large objects in the DB > (potentially tens or hundreds of gigs), and would like the=20 > pg_largeobject table to be stored on a separate FS. But of course=20 > it's not just one file to symlink and then forget about, it's a number=20 > of files that get created. >=20=20 > 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=20 > a kludge will do (or a patch come to that - we're runing redhat's=20 > 7.2.3 RPMs, but could switch if necessary). I had thought that if the=20 > filenames were predictable it might be possible to precreate a bunch=20 > of zero-length files and symlink them in advance... >=20=20 > Cheers >=20=20 > Matt >=20=20 >=20=20