pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Dawid Kuroczko <qnex42@gmail.com>
To: pgsql-performance@postgresql.org
Subject: Re: tablespace + RAM disk?
Date: Sat, 20 Nov 2004 10:36:38 +0100
Message-ID: <758d5e7f04112001361e517820@mail.gmail.com> (raw)
In-Reply-To: <07FDEE0ED7455A48AC42AC2070EDFF7C26BBCB@corpsrv2.tazznetworks.com>
References: <07FDEE0ED7455A48AC42AC2070EDFF7C26BBCB@corpsrv2.tazznetworks.com>

On Fri, 19 Nov 2004 23:18:51 -0500, David Parker
<dparker@tazznetworks.com> wrote:
> 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?
> 
> I can imagine doing it by having an initdb run at startup somehow, with
> the idea that having a mix of tablespaces in a database would make this
> harder, but I haven't read enough about tablespaces yet. The problem
> with trying to mix a RAM tablespace with a persistent tablespace would
> seem to be that you would have to recreate select data files at system
> startup before you could start the database. That's why an initdb seems
> cleaner to me, but...I should stop talking and go read about tablespaces
> and memcached.

I think there might be a problem with recovery after crash.  I haven't tested
it but I guess pgsql would complain that databases which existed before
crash (or even server reboot) no longer exist.  And I see two options, either
it would complain loudly and continue, or simply fail...  Unless there would
be option to mark database/schema/table as non-PITR-logged (since data
is expendable and can be easily recreated)... :)

Having tablespaces on RAM disks (like tmpfs), hmm, it could be useful,
say to put TEMPORARY tables there.  Since they will be gone nonetheless,
its a nice place for them.

Side question: Do TEMPORARY tables operations end up in PITR log?

   Regards,
       Dawid

PS: To pgmemchache I go!



view thread (7+ messages)  latest in thread

Message-ID: <758d5e7f04112001361e517820@mail.gmail.com>
Permalink:  ../758d5e7f04112001361e517820@mail.gmail.com/
Also on:    postgresql.org/message-id/758d5e7f04112001361e517820@mail.gmail.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: qnex42@gmail.com
  Subject: Re: tablespace + RAM disk?
  In-Reply-To: <758d5e7f04112001361e517820@mail.gmail.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