Date: Tue, 4 Mar 2014 08:24:15 -0800 (PST)
From: David Johnston <polobo@yahoo.com>
To: pgsql-admin@postgresql.org
Message-ID: <1393950255194-5794643.post@n5.nabble.com>
In-Reply-To: <5315EAF7.2060703@sorint.it>
References: 
 <B75CD08C73BD3543B97E4EF3964B7D701F79BDF8@CITESMBX1.ad.uillinois.edu>
 <5315EAF7.2060703@sorint.it>
Subject: Re: Enhancement Request
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Precedence: bulk
Sender: pgsql-admin-owner@postgresql.org

Marcello Lorenzi wrote
> Hi Lance,
> I don't know if you can create a tmpfs on your server and move the table 
> with a tablespace to the tmpfs mountpoint. In this case you can reach 
> the data on memory, but you have to mount and create the table to every 
> server restart.

Have you done this successfully, including failure testing?  If not then it
is not something you should recommend.  

Recent comments on the lists indicate that mounting tablespaces on volatile
filesystems is not a valid configuration since the tablespace and its
contents must be present as server startup.  You would never get a chance to
"create the table" since the server would not boot.

David J.


--
View this message in context: http://postgresql.1045698.n5.nabble.com/Enhancement-Request-tp5794609p5794643.html
Sent from the PostgreSQL - admin mailing list archive at Nabble.com.


-- 
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin