From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Bjorn T Johansen" <btj(at)havleik(dot)no> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Seq scan of table? |
Date: | 2003-09-05 06:44:51 |
Message-ID: | 9565.1062744291@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-performance |
"Bjorn T Johansen" <btj(at)havleik(dot)no> writes:
> I am trying to tune my database and I discovered one select that does a
> seq scan on a table but I can't see why... All the join fields are indexed
> and I am returning just one record, so no sort is done.
> Does it just pick seq scan for the heck of it or is it a reason?
Who's to say, when you gave us no details? Show us the table schemas,
the exact query, and EXPLAIN ANALYZE output, and you might get useful
responses.
(btw, pgsql-performance would be a more appropriate list for this issue
than pgsql-general.)
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Bjorn T Johansen | 2003-09-05 06:55:24 | Re: RE : Seq scan of table? |
Previous Message | Tom Lane | 2003-09-05 06:37:51 | Re: SQL Error: pqReadData() -- read() failed: errno=0 No error |
From | Date | Subject | |
---|---|---|---|
Next Message | Bjorn T Johansen | 2003-09-05 06:55:24 | Re: RE : Seq scan of table? |
Previous Message | Bruno BAGUETTE | 2003-09-05 06:34:47 | RE : Seq scan of table? |