Re: joining two tables slow due to sequential scan

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

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Scott Marlowe 2006-02-10 22:36:52 Re: joining two tables slow due to sequential scan
Previous Message Scott Marlowe 2006-02-10 22:22:05 Re: joining two tables slow due to sequential scan