Search Postgresql Archives

Re: why sequential scan is used on indexed column ???

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Michael Fuhr <mike@xxxxxxxx> schrieb:

> On Sat, Jun 14, 2008 at 04:59:44PM +0200, Andreas Kretschmer wrote:
> > Julius Tuskenis <julius.tuskenis@xxxxxxxxx> schrieb:
> > > I have a question concerning performance. One of my queries take a long  
> > > to execute. I tried to do "explain analyse" and I see that the  
> > > sequential scan is being used, although I have indexes set on columns  
> > > that are used in joins. The question is - WHY, and how to change that  
> > > behavior???
> > 
> > Try to create an index on apsilankymai.sas_id
> 
> In the DDL that Julius posted apsilankymai doesn't have an sas_id
> column.
> 
> The join is on apsilankymai.aps_saskaita = b_saskaita.sas_id.  Both
> columns have an index: b_saskaita.sas_id is a primary key so it
> should have an index implicitly, and apsilankymai.aps_saskaita has

Right, my mistake.


Andreas
-- 
Really, I'm not out to destroy Microsoft. That will just be a completely
unintentional side effect.                              (Linus Torvalds)
"If I was god, I would recompile penguin with --enable-fly."   (unknown)
Kaufbach, Saxony, Germany, Europe.              N 51.05082°, E 13.56889°


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux