Received: from localhost (unknown [200.46.204.187]) by postgresql.org (Postfix) with ESMTP id 0FFE69FB1D6 for ; Thu, 20 Sep 2007 16:34:44 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.187]) (amavisd-maia, port 10024) with ESMTP id 02335-07 for ; Thu, 20 Sep 2007 16:34:27 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from mail.net-domino.com (www.net-domino.com [74.208.11.96]) by postgresql.org (Postfix) with ESMTP id 0B7789FB268 for ; Thu, 20 Sep 2007 16:34:29 -0300 (ADT) Received: from [127.0.0.1] (u15245314.onlinehome-server.com [74.208.11.96]) by mail.net-domino.com (8.13.7/8.13.6) with ESMTP id l8KJYQHT022058; Thu, 20 Sep 2007 15:34:26 -0400 Message-ID: <46F2CB62.4020409@mochima.com> Date: Thu, 20 Sep 2007 15:34:58 -0400 From: Carlos Moreno User-Agent: Thunderbird 2.0.0.6 (X11/20070728) MIME-Version: 1.0 To: smiley2211 CC: pgsql-performance@postgresql.org Subject: Re: Upgraded from 7.4 to 8.1.4 QUERIES NOW SLOW!!! References: <12803859.post@talk.nabble.com> In-Reply-To: <12803859.post@talk.nabble.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Added-Header: Sample_milter accepted message X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200709/336 X-Sequence-Number: 26881 smiley2211 wrote: > Hello all, > > Old servers that housed 7.4 performed better than 8.1.4 version...are there > any MAJOR performance hits with this version??? > Are you using the default UNICODE encoding for your databases?? This could potentially translate into a performance hit (considerable? Maybe, depending on what your applications do) A related question: why not update to the latest, 8.2.x ?? > I set the postgresql.conf setting to equal that of 7.4 and queries still run > SLOW on 8.1.4... > Hmmm, I don't think the settings should be the same --- search the archives for discussions on performance tuning and an informal documentation of the postgresql.conf file. > 3) vacuum analyze > Am I understanding correctly that you did this?? Just to double check, yes, it is *very* important that you analyze the database *after loading it*. You could probably check the postgres log file to see if there are any obvious red flags in there. HTH, Carlos --