"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

• Re: OUTER JOIN performance regression remains in8.3beta4 at 2008-01-04 22:16:53 from Kevin Grittner

Responses

• Re: OUTER JOIN performance regression remains in8.3beta4 at 2008-01-04 22:44:27 from Kevin Grittner

pgsql-hackers by date

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

pgsql-patches by date

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