| From: | "Shridhar Daithankar" <shridhar_daithankar(at)persistent(dot)co(dot)in> |
|---|---|
| To: | pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: index / sequential scan problem |
| Date: | 2003-07-17 09:17:46 |
| Message-ID: | 3F16B712.19311.58D7530@localhost |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Paul Thomas | 2003-07-17 10:12:48 | Re: index / sequential scan problem |
| Previous Message | Fabian Kreitner | 2003-07-17 09:01:18 | index / sequential scan problem |