Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1TeNc4-00059J-3s for pgsql-performance@arkaria.postgresql.org; Fri, 30 Nov 2012 10:14:28 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.72) (envelope-from ) id 1TeNc3-0003Cl-7p for pgsql-performance@arkaria.postgresql.org; Fri, 30 Nov 2012 10:14:27 +0000 Received: from magus.postgresql.org ([87.238.57.229]) by malur.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1TeNc2-0003Cg-DM for pgsql-performance@postgresql.org; Fri, 30 Nov 2012 10:14:26 +0000 Received: from dub0-omc4-s6.dub0.hotmail.com ([157.55.2.81]) by magus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1TeNc0-00051X-7K for pgsql-performance@postgresql.org; Fri, 30 Nov 2012 10:14:26 +0000 Received: from DUB104-W41 ([157.55.2.71]) by dub0-omc4-s6.dub0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Fri, 30 Nov 2012 02:14:16 -0800 X-Originating-IP: [145.77.106.6] X-EIP: [o7OiKIkF+2S+dMtIVlNY21YR/DLMA45D] X-Originating-Email: [willem_leenen@hotmail.com] Message-ID: Content-Type: multipart/alternative; boundary="_fec2692d-8ee7-445e-8466-b0bc5ae967f5_" From: Willem Leenen To: , CC: , , Subject: Re: Optimize update query Date: Fri, 30 Nov 2012 10:14:15 +0000 Importance: Normal In-Reply-To: References: <20121130012426.69300@gmx.com>, , <855F8817-6C9A-4EFB-BB80-752BF7B73B56@autouncle.com>, MIME-Version: 1.0 X-OriginalArrivalTime: 30 Nov 2012 10:14:16.0409 (UTC) FILETIME=[7415B490:01CDCEE3] X-Pg-Spam-Score: -2.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 --_fec2692d-8ee7-445e-8466-b0bc5ae967f5_ Content-Type: text/plain; charset="ks_c_5601-1987" Content-Transfer-Encoding: 8bit Actually, what's the point in putting logs to ssd? SSDs are good for random access and logs are accessed sequentially. I'd put table spaces on ssd and leave logs on hdd 30 看盹研砌. 2012 04:33, "Niels Kristian Schj帚dt" 盼癸矜盹研. Because SSD's are considered faster. Then you have to put the most phyisical IO intensive operations on SSD. For the majority of databases, these are the logfiles. But you should investigate where the optimum is for your situation. --_fec2692d-8ee7-445e-8466-b0bc5ae967f5_ Content-Type: text/html; charset="ks_c_5601-1987" Content-Transfer-Encoding: 8bit

 Actually, what's the point in putting logs to ssd? SSDs are good for random access and logs are accessed sequentially. I'd put table spaces on ssd and leave logs on hdd
30 看盹研砌. 2012 04:33, "Niels Kristian Schj帚dt" <nielskristian@autouncle.com> 盼癸矜盹研.
Because SSD's are considered faster. Then you have to put the most phyisical IO intensive operations on SSD. For the majority of databases, these are the logfiles. But you should investigate where the optimum is for your situation.
 
--_fec2692d-8ee7-445e-8466-b0bc5ae967f5_--