Received: from makus.postgresql.org (makus.postgresql.org [98.129.198.125])
	by mail.postgresql.org (Postfix) with ESMTP id 1D38F159076
	for <pgsql-admin@postgresql.org>; Mon,  5 Mar 2012 09:28:08 -0400 (AST)
Received: from mail-pz0-f46.google.com ([209.85.210.46])
	by makus.postgresql.org with esmtp (Exim 4.72)
	(envelope-from <ruralhunter@gmail.com>) id 1S4XxO-0000lO-SZ
	for pgsql-admin@postgresql.org; Mon, 05 Mar 2012 13:28:07 +0000
Received: by dajr28 with SMTP id r28so6409523daj.33
	for <pgsql-admin@postgresql.org>; Mon, 05 Mar 2012 05:27:54 -0800 (PST)
Received-SPF: pass (google.com: domain of ruralhunter@gmail.com designates
	10.68.189.98 as permitted sender) client-ip=10.68.189.98;
Authentication-Results: mr.google.com;
	spf=pass (google.com: domain of ruralhunter@gmail.com
	designates 10.68.189.98 as permitted sender)
	smtp.mail=ruralhunter@gmail.com;
	dkim=pass header.i=ruralhunter@gmail.com
Received: from mr.google.com ([10.68.189.98])
	by 10.68.189.98 with SMTP id gh2mr17944658pbc.74.1330954074303
	(num_hops = 1); Mon, 05 Mar 2012 05:27:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=message-id:date:from:user-agent:mime-version:to:subject
	:content-type:content-transfer-encoding;
	bh=pIpKVJXIl5x1Vbmp1y+WA/6HFJZw4ec8ufl8eslc7Hw=;
	b=JTfKpGH4B0DvK7+DoPf2Fcf2qQMmzzvORni2YhTux4fPT03sUqSLmf/TULn7fnoofi
	KP5BJnD8aoUfewZfTBpvZyfQq0adBoXpKgJ39eN1JIcVjZaJJgIPYkONVjrAhk25LT/V
	ozYBkB/ppHNlwJ2LaaVGIUkNy8Lkwa11q5E41pg8IBVUM83KI+AkyzDxMdAHFtVa0dW9
	sr+V0gqHIvRUW88MjlJ1AUOFbg7smg7M6JonCwmtTHA9ciuDkLZxrxOJtrsQQLCnjsdm
	5OAy7wG0er4QuW12tgh5yArYLIA2pUcjg21REODOUBP6706hZ4wFICB9a62buvNTwJ6m
	oX2A==
Received: by 10.68.189.98 with SMTP id gh2mr15553333pbc.74.1330954074274;
	Mon, 05 Mar 2012 05:27:54 -0800 (PST)
Received: from [192.168.11.3] ([114.95.165.117])
	by mx.google.com with ESMTPS id k3sm13326002pbn.71.2012.03.05.05.27.50
	(version=TLSv1/SSLv3 cipher=OTHER);
	Mon, 05 Mar 2012 05:27:53 -0800 (PST)
Message-ID: <4F54BF4F.20308@gmail.com>
Date: Mon, 05 Mar 2012 21:27:43 +0800
From: Rural Hunter <ruralhunter@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1;
	rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: pgsql-admin@postgresql.org
Subject: Safe to put indexes in tablespaces on raid0 disk?
Content-Type: text/plain; charset=GB18030; format=flowed
Content-Transfer-Encoding: 7bit
X-Pg-Spam-Score: -2.6 (--)
X-Archive-Number: 201203/9
X-Sequence-Number: 39197

I want to separate my indexes into a tablespace which resides on a raid0 
disk for fast r/w access. Is it safe? what I mean is, if the raid0 disk 
is damaged, is it easy to recover the indexes by just recreating those 
indexes?