pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Josh Berkus <josh@agliodbs.com>
To: pgsql-performance@postgresql.org
Cc: David Parker <dparker@tazznetworks.com>
Subject: Re: tablespace + RAM disk?
Date: Sat, 20 Nov 2004 11:38:43 -0800
Message-ID: <200411201138.43162.josh@agliodbs.com> (raw)
In-Reply-To: <07FDEE0ED7455A48AC42AC2070EDFF7C26BBCB@corpsrv2.tazznetworks.com>
References: <07FDEE0ED7455A48AC42AC2070EDFF7C26BBCB@corpsrv2.tazznetworks.com>

David,

> But, I'm also still interested in the answer to my question: is there
> any reason you could not put an 8.0 tablespace on a RAM disk?

Some people have *talked* about trying it, but nobody yet has reported back.  
I can see a few potential problems:

1) The query planner would not be aware, and could not be made aware short of 
hacking the source, that one tablespace has different access speeds than the 
others;

2) After a crash, you might be unable to recover that tablespace, and PG would 
refuse to bring the system back up without it.

However, the best thing to do is to try it.  Good luck, and do a write-up for 
us!

-- 
Josh Berkus
Aglio Database Solutions
San Francisco



view thread (7+ messages)  latest in thread

Message-ID: <200411201138.43162.josh@agliodbs.com>
Permalink:  ../200411201138.43162.josh@agliodbs.com/
Also on:    postgresql.org/message-id/200411201138.43162.josh@agliodbs.com

 · 

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 using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: josh@agliodbs.com, dparker@tazznetworks.com
  Subject: Re: tablespace + RAM disk?
  In-Reply-To: <200411201138.43162.josh@agliodbs.com>

* 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