Received: from maia.hub.org (maia-5.hub.org [200.46.204.29]) by mail.postgresql.org (Postfix) with ESMTP id 88816640989 for ; Thu, 10 Jun 2010 17:16:01 -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 82544-05 for ; Thu, 10 Jun 2010 20:15:54 +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 CBC90640968 for ; Thu, 10 Jun 2010 17:15:53 -0300 (ADT) Received: from [192.168.1.6] (pool-96-244-14-10.bltmmd.fios.verizon.net [96.244.14.10]) by mrelayeu.kundenserver.de (node=mrbap2) with ESMTP (Nemesis) id 0LiJAx-1P0rjN0BQx-00nQV4; Thu, 10 Jun 2010 22:15:46 +0200 Message-ID: <4C1147F0.2090607@2ndquadrant.com> Date: Thu, 10 Jun 2010 16:15:44 -0400 From: Greg Smith User-Agent: Thunderbird 2.0.0.24 (X11/20100317) MIME-Version: 1.0 To: Max Williams CC: "pgsql-performance@postgresql.org" Subject: Re: Large (almost 50%!) performance drop after upgrading to 8.4.4? References: <0357196CB603794BB76F4F6B373F27330506EACE45@SERVER.ddnglobal.local> <1276158598.5764.22.camel@hp-laptop2.gunduz.org> <0357196CB603794BB76F4F6B373F27330506EACE51@SERVER.ddnglobal.local> <15383.1276179056@sss.pgh.pa.us> <0357196CB603794BB76F4F6B373F27330506EACE55@SERVER.ddnglobal.local> <4C10BB59020000250003214A@gw.wicourts.gov> <0357196CB603794BB76F4F6B373F27330506EACE56@SERVER.ddnglobal.local> In-Reply-To: <0357196CB603794BB76F4F6B373F27330506EACE56@SERVER.ddnglobal.local> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V01U2FsdGVkX1+LkUkiMFqCb9XTYfmhOKPtArgDX/wLjDgpHJN WRzUFQDAPh3Benh52LOSUD+Zy8PvdBvHCy8tQ2asuHEI5F92BT 0C27OQ4e+z1tAsXFEHMnlvliqKYPssX X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=1.794 tagged_above=-10 required=5 tests=BAYES_50=0.8, PLING_QUERY=0.994, RCVD_IN_DNSWL_NONE=-0.0001 X-Spam-Level: * X-Archive-Number: 201006/188 X-Sequence-Number: 39044 Max Williams wrote: > Can I just turn this off on 8.4.4 or is it a compile time option You can update your postgresql.conf to include: debug_assertions = false And restart the server. This will buy you back *some* of the performance loss but not all of it. Will have to wait for corrected packaged to make the issue completely go away. -- Greg Smith 2ndQuadrant US Baltimore, MD PostgreSQL Training, Services and Support greg@2ndQuadrant.com www.2ndQuadrant.us