Re: joining two tables slow due to sequential scan - Mailing list pgsql-performance

From Scott Marlowe
Subject Re: joining two tables slow due to sequential scan
Date
Msg-id 1139611012.22740.147.camel@state.g2switchworks.com
Whole thread Raw
In response to Re: joining two tables slow due to sequential scan  ("Tim Jones" <TJones@optio.com>)
List pgsql-performance
On Fri, 2006-02-10 at 16:35, Tim Jones wrote:
> OK.  I'm gonna make a couple of guesses here:
>
> 1:  clinicaldocuments.patientidentifier is an int8 and you're running
> 7.4 or before.
>
> -- nope int4  and 8.1
>
> 2: There are more rows with clinicaldocuments.patientidentifier= 123
> than with documentversions.documentstatus = 'AC'.
>
> -- nope generally speaking all statuses are 'AC'
>
> 3: documentversions.documentidentifier and
> clinicaldocuments.dssdocumentidentifier are not the same type.
>
> -- nope both int4

OK then, I guess we'll need to see the explain analyze output of both of
those queries.

pgsql-performance by date:

Previous
From: "Tim Jones"
Date:
Subject: Re: joining two tables slow due to sequential scan
Next
From: "Tim Jones"
Date:
Subject: Re: joining two tables slow due to sequential scan