From: | "EDMUND DENGLER" <edmundd(at)esentire(dot)com> |
---|---|
To: | mcauleyt(at)tcd(dot)ie |
Subject: | Re: Unused Indexes |
Date: | 2003-07-30 13:49:54 |
Message-ID: | 20030730135052.6B6D5D1C4CB@svr1.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
You need to convert the int's to bigints.
select id where col1 = 1::bigint and col2 = 1::bigint
Regards,
Ed
-----Original Message-----
From: Tim McAuley <mcauleyt(at)tcd(dot)ie>
Date: Wed, 30 Jul 2003 13:46:46
To:pgsql-general(at)postgresql(dot)org
Subject: [GENERAL] Unused Indexes
Hi,
I have a table which I have populated with over 5000 entries. There is a
combined index placed on two of the columns (both bigint). I am trying
a simple select (i.e. select id where col1 = 1 and col2 = 1) covering
these two columns and it keeps using a seq scan. Is this correct? I
would have thought that with this number of entries that an index scan
should be used.
I am testing this using postgresql 7.3.3 on windows 2000 using cygwin.
Doing "set enable_seqscan to off" does not change the results of the
explain operation.
I also tried setting a single index on just one of the columns and
running an appropriate search; it still uses a seq scan. At what stage
will the planner normally start using an index scan?
Any hints appreciated.
Tim
---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster
From | Date | Subject | |
---|---|---|---|
Next Message | Tim McAuley | 2003-07-30 14:06:05 | Re: Unused Indexes |
Previous Message | Christopher Murtagh | 2003-07-30 13:30:06 | Changing DB ownership |