X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 24F103A4A26 for ; Sat, 20 Nov 2004 09:36:48 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 76840-07 for ; Sat, 20 Nov 2004 09:36:37 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.199]) by svr1.postgresql.org (Postfix) with ESMTP id 46EC93A3AFE for ; Sat, 20 Nov 2004 09:36:38 +0000 (GMT) Received: by rproxy.gmail.com with SMTP id a36so101209rnf for ; Sat, 20 Nov 2004 01:36:38 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=IJjWyZSRPsMcdPdY+o8DoiKUB1uZ5tJAUIAj7lrmpimE4ocmAsFB5NPVyO1X8m+/aDWXMyxR9eIdPRuNkZbzsp5bQQ2u84xDvxYhaBubiAbglWkOsPgz7WQpPoUk67m0Jv2Ya1JjT8BGBCU8gEO3NAlvTeXr3ze+5rT7ZxnG+pI= Received: by 10.38.77.37 with SMTP id z37mr77428rna; Sat, 20 Nov 2004 01:36:38 -0800 (PST) Received: by 10.38.163.22 with HTTP; Sat, 20 Nov 2004 01:36:38 -0800 (PST) Message-ID: <758d5e7f04112001361e517820@mail.gmail.com> Date: Sat, 20 Nov 2004 10:36:38 +0100 From: Dawid Kuroczko Reply-To: Dawid Kuroczko To: pgsql-performance@postgresql.org Subject: Re: tablespace + RAM disk? In-Reply-To: <07FDEE0ED7455A48AC42AC2070EDFF7C26BBCB@corpsrv2.tazznetworks.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <07FDEE0ED7455A48AC42AC2070EDFF7C26BBCB@corpsrv2.tazznetworks.com> X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.9 tagged_above=0.0 required=5.0 tests=FROM_ENDS_IN_NUMS X-Spam-Level: X-Archive-Number: 200411/317 X-Sequence-Number: 9271 On Fri, 19 Nov 2004 23:18:51 -0500, David Parker 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!