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

From Tim Jones
Subject Re: joining two tables slow due to sequential scan
Date
Msg-id 47668A1334CDBF46927C1A0DFEB223D3131315@mail.optiosoftware.com
Whole thread Raw
In response to joining two tables slow due to sequential scan  ("Tim Jones" <TJones@optio.com>)
Responses Re: joining two tables slow due to sequential scan
List pgsql-performance

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

Any of those things true?

pgsql-performance by date:

Previous
From: Scott Marlowe
Date:
Subject: Re: joining two tables slow due to sequential scan
Next
From: Scott Marlowe
Date:
Subject: Re: joining two tables slow due to sequential scan