Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!aioe.org!.POSTED!not-for-mail
From: Don Y <nowhere@here.com>
Newsgroups: comp.databases.postgresql
Subject: Constraints for R/O ./data/{base, et al.}
Date: Wed, 28 Sep 2011 08:58:31 -0700
Organization: Aioe.org NNTP Server
Lines: 14
Message-ID: <j5vg74$fbf$1@speranza.aioe.org>
NNTP-Posting-Host: 4Z1anTAvuKQjXSMvG5DkQg.user.speranza.aioe.org
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Complaints-To: abuse@aioe.org
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
X-Notice: Filtered by postfilter v. 0.8.2
Xref: x330-a1.tempe.blueboxinc.net comp.databases.postgresql:252

Hi,

Given largely static tables (etc.), how much of ./data
can I move onto R/O media?  And, which types of operations
would a user then have to avoid?

Loosening constraints a little, how much more could a user
do if the R/O media was just "very slowly writable" media?

Finally, what operations *require* the fastest media updates
(i.e., "RAM")?

Thx,
--don