Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1Ubz32-0004Bm-2Y for pgsql-performance@arkaria.postgresql.org; Mon, 13 May 2013 20:08:40 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.72) (envelope-from ) id 1Ubz31-0005tM-Jj for pgsql-performance@arkaria.postgresql.org; Mon, 13 May 2013 20:08:39 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1Ubz30-0005tH-Hx for pgsql-performance@postgresql.org; Mon, 13 May 2013 20:08:38 +0000 Received: from out1-smtp.messagingengine.com ([66.111.4.25]) by magus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1Ubz2p-00061c-5n for pgsql-performance@postgresql.org; Mon, 13 May 2013 20:08:38 +0000 Received: from compute1.internal (compute1.nyi.mail.srv.osa [10.202.2.41]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id B556C20905 for ; Mon, 13 May 2013 16:08:24 -0400 (EDT) Received: from frontend1.nyi.mail.srv.osa ([10.202.2.160]) by compute1.internal (MEProxy); Mon, 13 May 2013 16:08:24 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=feld.me; h= content-type:to:subject:references:date:mime-version :content-transfer-encoding:from:message-id:in-reply-to; s= mesmtp; bh=KERWlex/MhUBGKCRCHaSGAiWsnU=; b=lyf6lP2HWVD4S2cr9nnyz rZ+7Dncu5pdC+vaTCHm7hLnOoX1E/vddY/6/DwjkCIhw+LbQXGKU3hsAgMCKxmZc z0XPgm/AlXyujD8RV/jeM5THKVRxPptpSn/CE19jjxl8SPx70aP97T09eo/1sr0w KV0FVG5pryHPp6DRJ+TPCc= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=content-type:to:subject:references:date :mime-version:content-transfer-encoding:from:message-id :in-reply-to; s=smtpout; bh=KERWlex/MhUBGKCRCHaSGAiWsnU=; b=nsCg A2QDTagYu/hA/08VD421pVUR3jTjLfL7+WffrVjgT7vVHA50vbSNfPTs8RXkFAoZ ldWL26ntrwXYh18jj84JpeZ5Aa1/o7Bg6+iP0hzA/6zfK6eiE8E9CRT8sIzDDIHC tKio/dEJsuviWCMe+HTBeaIBYeuGXAKoxsQpr00= X-Sasl-enc: K3dOhKHS3RU3cjXiVuJmQXyLRsEzCRNVz/LxpOOKq5VQ 1368475704 Received: from markf.office.supranet.net (unknown [66.170.8.18]) by mail.messagingengine.com (Postfix) with ESMTPA id 732E7C80005 for ; Mon, 13 May 2013 16:08:24 -0400 (EDT) Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes To: pgsql-performance@postgresql.org Subject: Re: RT3.4 query needed a lot more tuning with 9.2 than it did with 8.1 References: <20130430112055.GA27525@msgid.df7cb.de> Date: Mon, 13 May 2013 15:08:23 -0500 MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: "Mark Felder" Message-ID: In-Reply-To: <20130430112055.GA27525@msgid.df7cb.de> User-Agent: Opera Mail/12.15 (FreeBSD) X-Pg-Spam-Score: -2.7 (--) 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 On Tue, 30 Apr 2013 06:20:55 -0500, Christoph Berg wrote: > Hi, > this is more of a report than a question, because we thought this > would be interesting to share. > We recently (finally) migrated an Request Tracker 3.4 database running > on 8.1.19 to 9.2.4. The queries used by rt3.4 are sometimes weird, but > 8.1 coped without too much tuning. The schema looks like this: What version of DBIx-SearchBuilder do you have on that server? The RT guys usually recommend you have the latest possible so RT is performing the most sane/optimized queries possible for your database. I honestly don't know if it will make a difference for you, but it's worth a shot. -- Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance