Re: joining two tables slow due to sequential scan

From: Scott Marlowe <smarlowe(at)g2switchworks(dot)com>
To: Tim Jones <TJones(at)optio(dot)com>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: joining two tables slow due to sequential scan
Date: 2006-02-10 22:36:52
Message-ID: 1139611012.22740.147.camel@state.g2switchworks.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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.

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Tim Jones 2006-02-10 22:37:32 Re: joining two tables slow due to sequential scan
Previous Message Tim Jones 2006-02-10 22:35:50 Re: joining two tables slow due to sequential scan