Received: from magus.postgresql.org (magus.postgresql.org [87.238.57.229]) by mail.postgresql.org (Postfix) with ESMTP id 6136D159078 for ; Mon, 5 Mar 2012 12:50:30 -0400 (AST) Received: from mail-pz0-f46.google.com ([209.85.210.46]) by magus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1S4b79-00050Y-Ej for pgsql-admin@postgresql.org; Mon, 05 Mar 2012 16:50:29 +0000 Received: by dajr28 with SMTP id r28so6641597daj.33 for ; Mon, 05 Mar 2012 08:50:09 -0800 (PST) Received-SPF: pass (google.com: domain of ruralhunter@gmail.com designates 10.68.129.228 as permitted sender) client-ip=10.68.129.228; Authentication-Results: mr.google.com; spf=pass (google.com: domain of ruralhunter@gmail.com designates 10.68.129.228 as permitted sender) smtp.mail=ruralhunter@gmail.com; dkim=pass header.i=ruralhunter@gmail.com Received: from mr.google.com ([10.68.129.228]) by 10.68.129.228 with SMTP id nz4mr52103115pbb.91.1330966209536 (num_hops = 1); Mon, 05 Mar 2012 08:50:09 -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:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=caOTuIsLwdFDrbWaCtJ0Ygz0620kMFl5jLKAzGJDg9o=; b=FhT7sOj3w9Hlt7SHYlMqOai0W7aXFuDdXSMLLweqfwzlWGftsShNK7exLeM7SQucAJ LQSmTB5i7nRiUvnG56+DM7lWjLvmhifvNzaGW1OA8wTfmqRzt91ZLKeJry8j+vpYFwbW s52biPTZsieAiABtmJkwgIkts+JBT3cGPNuZmhIQyZ19mJuZXB3Twmw5Q0eo2fx2eq5/ jEcMbvVSZicB98AYwpqGKyYxPyR4zOBSytNSuzQB3YyFL2Y4WL6AFlwp1QtfBEHW5VZJ SCwz99qWZzZ7Ui3Ru22smcQkcOQ/+oUpLRAhuZZnUwpEGnaawkarx3gtqmSMOl5tkC88 SkhA== Received: by 10.68.129.228 with SMTP id nz4mr44625430pbb.91.1330966209488; Mon, 05 Mar 2012 08:50:09 -0800 (PST) Received: from [192.168.11.3] ([114.95.165.117]) by mx.google.com with ESMTPS id l8sm13766172pbi.0.2012.03.05.08.50.05 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 05 Mar 2012 08:50:08 -0800 (PST) Message-ID: <4F54EEB8.7070105@gmail.com> Date: Tue, 06 Mar 2012 00:50:00 +0800 From: Rural Hunter User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2 MIME-Version: 1.0 To: "Nicholson, Brad (Toronto, ON, CA)" CC: "pgsql-admin@postgresql.org" Subject: Re: Safe to put indexes in tablespaces on raid0 disk? References: <4F54BF4F.20308@gmail.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Pg-Spam-Score: -2.7 (--) X-Archive-Number: 201203/11 X-Sequence-Number: 39199 thanks. temporarily not having the indexes should be fine to me. 于2012年3月5日 23:53:52,Nicholson, Brad (Toronto, ON, CA)写到: >> -----Original Message----- >> From: pgsql-admin-owner@postgresql.org [mailto:pgsql-admin- >> owner@postgresql.org] On Behalf Of Rural Hunter >> Sent: Monday, March 05, 2012 8:28 AM >> To: pgsql-admin@postgresql.org >> Subject: [ADMIN] Safe to put indexes in tablespaces on raid0 disk? >> >> 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? > > You should be fine doing this from a technical perspective. Make sure you think about the impact of temporarily not having the indexes in place. Can you keep your system down while you rebuild the indexes? Can you limp by while you are rebuilding the indexes? > > Brad. >