Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1UFrGp-0004aB-Ed for pgsql-performance@arkaria.postgresql.org; Wed, 13 Mar 2013 19:23:27 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.72) (envelope-from ) id 1UFrGo-0007Hs-SJ for pgsql-performance@arkaria.postgresql.org; Wed, 13 Mar 2013 19:23:26 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1UFrGn-0007Hm-C8 for pgsql-performance@postgresql.org; Wed, 13 Mar 2013 19:23:25 +0000 Received: from cerberus.pinpointresearch.com ([66.7.238.130] helo=polaris.pinpointresearch.com) by magus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1UFrGi-0005cG-MA for pgsql-performance@postgresql.org; Wed, 13 Mar 2013 19:23:24 +0000 Received: from [192.168.1.179] (betelgeuse.pinpointresearch.com [192.168.1.179]) by polaris.pinpointresearch.com (Postfix) with ESMTP id 634EFE00EC83 for ; Wed, 13 Mar 2013 12:23:18 -0700 (PDT) Message-ID: <5140D226.4060609@pinpointresearch.com> Date: Wed, 13 Mar 2013 12:23:18 -0700 From: Steve Crawford User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130221 Thunderbird/17.0.3 MIME-Version: 1.0 To: pgsql-performance@postgresql.org Subject: Re: New server setup References: <4D6D1410-2208-4DAA-BD64-69BE1FD94E55@autouncle.com> <513CADB7.4030803@2ndQuadrant.com> <51409C51.1070601@kickstone.com> <38D48FB0-92A8-433B-8D34-4C63738B45BA@gmail.com> <5140A623.20005@kickstone.com> In-Reply-To: <5140A623.20005@kickstone.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Pg-Spam-Score: -4.3 (----) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-performance Precedence: bulk Sender: pgsql-performance-owner@postgresql.org On 03/13/2013 09:15 AM, John Lister wrote: > On 13/03/2013 15:50, Greg Jaskiewicz wrote: >> SSDs have much shorter life then spinning drives, so what do you do >> when one inevitably fails in your system ? > Define much shorter? I accept they have a limited no of writes, but > that depends on load. You can actively monitor the drives "health" > level... What concerns me more than wear is this: InfoWorld Article: http://www.infoworld.com/t/solid-state-drives/test-your-ssds-or-risk-massive-data-loss-researchers-warn-213715 Referenced research paper: https://www.usenix.org/conference/fast13/understanding-robustness-ssds-under-power-fault Kind of messes with the "D" in ACID. Cheers, Steve -- Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance