Received: from maia.hub.org (maia-5.hub.org [200.46.204.29]) by mail.postgresql.org (Postfix) with ESMTP id E3C1AB5DBFC for ; Thu, 8 Sep 2011 22:28:48 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.29]) (amavisd-maia, port 10024) with ESMTP id 71395-07 for ; Fri, 9 Sep 2011 01:28:42 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.186]) by mail.postgresql.org (Postfix) with ESMTP id 4FEF3B5DBDA for ; Thu, 8 Sep 2011 22:28:42 -0300 (ADT) Received: from [192.168.1.7] (mail.highperformancepostgresql.com [71.179.240.8]) by mrelayeu.kundenserver.de (node=mrbap2) with ESMTP (Nemesis) id 0MCx2B-1QtH3a2WmJ-009R9G; Fri, 09 Sep 2011 03:28:42 +0200 Message-ID: <4E696BC8.3030905@2ndQuadrant.com> Date: Thu, 08 Sep 2011 21:28:40 -0400 From: Greg Smith User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.16) Gecko/20110818 Icedove/3.0.11 MIME-Version: 1.0 To: pgsql-performance@postgresql.org Subject: Re: how delete/insert/update affects select performace? References: <004301cc6e26$015a75e0$040f61a0$@devshock.com> <4E688FFC0200002500040F10@gw.wicourts.gov> <012001cc6e45$fa57f950$ef07ebf0$@devshock.com> In-Reply-To: <012001cc6e45$fa57f950$ef07ebf0$@devshock.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V02:K0:n7UVJuvDlD5RIU+S1Hjf8n8L6AFx6ASyAX0pAvq0pjA NopYeU6N/82ke6ebztkZOWdGxbtJ7cXUI0Cued3QOLbiYjCh7j s7YP58EKLKZU8tFBA1OiFdqahfS7hR7S+39JJ50L54P/QcpMSF wx1UFtn5zrKtbrH1r3UY8oVxlYVEyD4u3eauJhjJnopR+VCNry 6LmCCnEBP4fdjZRc+WUr+g47UjkWXqMPEQlZ2AOPTJVR3sk7IN hVYd8/al1oeFLlhc0dXcAVdPVC3VL4B/YtmWuLvKv3fmlFO+eg jPYo+E8sdcMp1wMLD7ABhE8bIoe50/Tcxzo73++FrWQfPJrN0l zCPESCtgqrbNEhJbf8NI= X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.9 tagged_above=-10 required=5 tests=BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001 X-Spam-Level: X-Archive-Number: 201109/85 X-Sequence-Number: 44861 On 09/08/2011 12:40 PM, Anibal David Acosta wrote: > Postgres 9.0 on windows server 2008 r2 > HW is a dell dual processor with 16gb of ram . > The general guidelines for Windows servers such as http://wiki.postgresql.org/wiki/Tuning_Your_PostgreSQL_Server recommend a fairly small setting for the shared_buffers parameters on Windows--no more than 512MB. That makes your server a bit less likely to run in the nasty checkpoint spike issues Kevin was alluding to. I don't think we've seen any reports of that on Windows. The problem is worst on Linux. -- Greg Smith 2ndQuadrant US greg@2ndQuadrant.com Baltimore, MD PostgreSQL Training, Services, and 24x7 Support www.2ndQuadrant.us