| From: | "Bjorn T Johansen" <btj(at)havleik(dot)no> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Seq scan of table? |
| Date: | 2003-09-05 06:57:55 |
| Message-ID: | 14399.193.212.14.12.1062745075.squirrel@www.havleik.no |
| Views: | Whole Thread | Raw Message | 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
>
Well, since the select involves 10-12 tables and a large sql, I just
thought I would try without all that information first... :)
And yes, pgsql-performance sounds like the right list....
BTJ
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alessandro GARDICH | 2003-09-05 07:21:07 | notify problem |
| Previous Message | Bjorn T Johansen | 2003-09-05 06:55:24 | Re: RE : Seq scan of table? |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Richard Huxton | 2003-09-05 08:34:52 | Re: Performance problems on a fairly big table with two key columns. |
| Previous Message | Bjorn T Johansen | 2003-09-05 06:55:24 | Re: RE : Seq scan of table? |