pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Matt Clark <matt@ymogen.net>
To: 'Bradley Kieser' <brad@kieser.net>
Cc: pgsql-admin@postgresql.org
Cc: emberson@phc.net
Subject: Re: Postgres & large objects
Date: Thu, 6 May 2004 10:31:00 +0100
Message-ID: <008101c4334c$d834da50$8300a8c0@solent> (raw)
In-Reply-To: <409A0D6D.3040200@kieser.net>

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.  

M

-----Original Message-----
From: Bradley Kieser [mailto:brad@kieser.net] 
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 
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
>  
>  






view thread (3+ messages)  latest in thread

Message-ID: <008101c4334c$d834da50$8300a8c0@solent>
Permalink:  ../008101c4334c$d834da50$8300a8c0@solent/
Also on:    postgresql.org/message-id/008101c4334c$d834da50$8300a8c0@solent

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: matt@ymogen.net, brad@kieser.net, emberson@phc.net
  Subject: Re: Postgres & large objects
  In-Reply-To: <008101c4334c$d834da50$8300a8c0@solent>
  References: <409A0D6D.3040200@kieser.net> <008101c4334c$d834da50$8300a8c0@solent>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox