Re: index / sequential scan problem - Mailing list pgsql-performance

From Shridhar Daithankar
Subject Re: index / sequential scan problem
Date
Msg-id 3F16B712.19311.58D7530@localhost
Whole thread Raw
In response to index / sequential scan problem  (Fabian Kreitner <fabian.kreitner@ainea-ag.de>)
Responses Re: index / sequential scan problem
List pgsql-performance
On 17 Jul 2003 at 11:01, Fabian Kreitner wrote:
> psql (PostgreSQL) 7.2.2
>
> perg_1097=# VACUUM ANALYZE ;
> VACUUM
> perg_1097=# EXPLAIN ANALYZE    select  notiz_id, obj_id, obj_typ
> perg_1097-#     from    notiz_objekt a
> perg_1097-#     where not exists
> perg_1097-#     (
> perg_1097(#       select  1
> perg_1097(#       from    notiz_gelesen b
> perg_1097(#       where   ma_id  = 2001
> perg_1097(#       and     ma_pid = 1097
> perg_1097(#       and     a.notiz_id = b.notiz_id
> perg_1097(#     )
> perg_1097-# ;

For 31K records, seq. scan does not sound like a bad plan to me but anyway..

How about

 where   ma_id  = 2001::integer
and     ma_pid = 1097::integer

in above query?

Bye
 Shridhar

--
No one can guarantee the actions of another.        -- Spock, "Day of the Dove",
stardate unknown


pgsql-performance by date:

Previous
From: Fabian Kreitner
Date:
Subject: index / sequential scan problem
Next
From: Paul Thomas
Date:
Subject: Re: index / sequential scan problem