Re: OUTER JOIN performance regression remains in 8.3beta4

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
Cc: pgsql-hackers(at)postgresql(dot)org, "Kevin Grittner" <Kgrittn(dot)CCAP(dot)Courts(at)wicourts(dot)gov>
Subject: Re: OUTER JOIN performance regression remains in 8.3beta4
Date: 2008-01-04 22:40:22
Message-ID: 23936.1199486422@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

"Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> writes:
> As I poked around at this, it started to seem familiar. I had
> previously posted about this query's performance under 8.2.4.
> http://archives.postgresql.org/pgsql-performance/2007-10/msg00087.php

Well, that thread gave some of the missing details, such as

Table "public.ControlRecord"
Column | Type | Modifiers
--------------------+------------------------+-----------
countyNo | "CountyNoT" | not null

but what the heck is "CountyNoT"?

It looks like 8.3 is failing to realize that it can propagate the
countyNo = 53 condition down to this table's scan, as 8.2 did;
but there's not enough details here to guess why not.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Kevin Grittner 2008-01-04 22:42:16 Re: OUTER JOIN performance regression remains in 8.3beta4
Previous Message Tom Lane 2008-01-04 22:29:32 Re: OUTER JOIN performance regression remains in 8.3beta4

Browse pgsql-patches by date

  From Date Subject
Next Message Kevin Grittner 2008-01-04 22:42:16 Re: OUTER JOIN performance regression remains in 8.3beta4
Previous Message Tom Lane 2008-01-04 22:29:32 Re: OUTER JOIN performance regression remains in 8.3beta4