Received: from localhost (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id E0157635AF6 for ; Thu, 5 Mar 2009 14:14:08 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 08221-06-4 for ; Thu, 5 Mar 2009 14:14:06 -0400 (AST) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from mail-qy0-f135.google.com (mail-qy0-f135.google.com [209.85.221.135]) by mail.postgresql.org (Postfix) with ESMTP id E2A72635DD0 for ; Thu, 5 Mar 2009 12:56:19 -0400 (AST) Received: by qyk41 with SMTP id 41so4784qyk.15 for ; Thu, 05 Mar 2009 08:56:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=fnQTLVT3EwaVC1a/nNwn7cREif5lGbU01kK3gjlFPqA=; b=iRKpFCnS5YXURMxt49a0p48RkbFyY5f6q3/DVdkQNg2j0vTIq0LM3VIYv2ddkl/RFD LpAMDwj5TGV72iQhww7VdwtS75+yi1DBZ9uyDfyjvZD4AQE2Vt2LwcReLD6p3yBzxp23 gWQSsI7tpF1T3Jtr7xbiHgsnS5+6GZJLL2iSQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=j26P6jCQHTNBjLIYrHRySDTvqj84QKXLHQoWpI/c1UQ41DgPT+XJ7aoit5aQxBABM4 jd8wZSmHgrmpNDD7KavPKhIEoVNw7HvFNIN2CPARGlfM18+aelOdy7nmoM1Tj2Bvjsv+ ATEKeTEHOnZJeHQEz4K77EbnKea7cIeAMeLj8= MIME-Version: 1.0 Received: by 10.229.84.72 with SMTP id i8mr833902qcl.63.1236272168363; Thu, 05 Mar 2009 08:56:08 -0800 (PST) In-Reply-To: <49AF9952.EE98.0025.0@wicourts.gov> References: <2870.1236050632@sss.pgh.pa.us> <17797.1236119652@sss.pgh.pa.us> <603c8f070903050521q64ea85efnff129b1cb6d5c502@mail.gmail.com> <49AF9952.EE98.0025.0@wicourts.gov> Date: Thu, 5 Mar 2009 11:56:08 -0500 Message-ID: <603c8f070903050856y37d9825bga53fcc2017143163@mail.gmail.com> Subject: Re: Postgres 8.3, four times slower queries? From: Robert Haas To: Kevin Grittner Cc: Aaron Guyon , pgsql-performance@postgresql.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none X-Spam-Level: X-Archive-Number: 200903/50 X-Sequence-Number: 32972 On Thu, Mar 5, 2009 at 10:20 AM, Kevin Grittner wrote: >>>> Robert Haas wrote: >> Well, it looks like the problem is that 8.3 is not using the index >> idx_bundle_content_bundle_id. =A0But I don't know why that should be >> happening, unless there's a problem with that index. > > I didn't see that index defined. =A0In fact, in the query shown, t8 is > the payment_amount table, but in plan, I don't see any references to > that table, and t8 is a table called bundle_content which is not > included. Good point. Now that you mention it, I notice that many of the tables and columns seem to have been renamed. It's pretty hard to make anything intelligible out of a schema that doesn't resemble the plan. ...Robert