Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1Upky6-0007jH-7x for pgsql-performance@arkaria.postgresql.org; Thu, 20 Jun 2013 19:56:30 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1Upky4-0002xP-T0 for pgsql-performance@arkaria.postgresql.org; Thu, 20 Jun 2013 19:56:28 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1Upky2-0002xG-PJ for pgsql-performance@postgresql.org; Thu, 20 Jun 2013 19:56:26 +0000 Received: from mail-ie0-x22f.google.com ([2607:f8b0:4001:c03::22f]) by magus.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1Upkxs-0005OE-CB for pgsql-performance@postgresql.org; Thu, 20 Jun 2013 19:56:23 +0000 Received: by mail-ie0-f175.google.com with SMTP id a13so17350424iee.20 for ; Thu, 20 Jun 2013 12:56:15 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding:x-gm-message-state; bh=RsCAm02LV/rn092mV9C/Ct3sCjX05Uy3CWZYHhkFnnA=; b=Y3NZgp1z7ZKQtxdEocHBoI5YNywJ7/c1qDTIMt2akaivHwQgDFEDCC9qR3ZyqhVY/q 6WKm9B3Gfq672xnFHFcLDKsZMBsPWFGgXzztzLjyQ+rF8db59OtOC9LvdoHmvLA2RQtD QWfcNWWWn+XI+4sB6Fnfq01DsPPHTMdysdzVSIZDgmpe2yrsgzYPRSBdvTEQPqrRK21K V1hw1iqciHQSflipJ8xoKOYUF8zFR93sJ2eXcbKY34kgiFsn83HbQ7bKyvZNi7801wTF Af5vw1sO5QP+6NAplXUi6CEPJBgGaAfLWLigPN4aaJlZHnQvpNJQI9/ycqhw8Z+ybYfK 7eyQ== X-Received: by 10.43.130.5 with SMTP id hk5mr733823icc.116.1371758175101; Thu, 20 Jun 2013 12:56:15 -0700 (PDT) Received: from Kevins-MacBook-Pro.local (216-98-193-98.static.forethought.net. [216.98.193.98]) by mx.google.com with ESMTPSA id wn10sm12412029igb.2.2013.06.20.12.56.13 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 20 Jun 2013 12:56:14 -0700 (PDT) Message-ID: <51C35E6C.1090705@consistentstate.com> Date: Thu, 20 Jun 2013 13:56:28 -0600 From: CS DBA User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: pgsql-performance@postgresql.org Subject: PostgreSQL settings for running on an SSD drive Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Gm-Message-State: ALoCoQlQKdpu5wO+Qj0RZ5gdG/WgPjeJgseXUBl4GK6MQbR7xEbFQHHd7qPVqD/Kp6j4Z0pvuJdO X-Pg-Spam-Score: -1.9 (-) 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 All; I'm working with a client running PostgreSQL on a Fusion-IO drive. They have a PostgreSQL setup guide from Fusion recommending the following settings: effective_io_concurrency=0 bgwriter_lru_maxpages=0 random_page_cost=0.1 sequential_page_cost=0.1
 These seem odd to me, effectively turning the background writer off, plus setting both random_page_cost and sequential_page_cost to the same (very low) value... Thoughts? Thanks in advance -- Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance