Elielson Fontanezi <[EMAIL PROTECTED]> writes:
> Hum... What such thing strange.
> Hash algorithms should be better than BTREE and RTREE algorithms.
Perhaps. The problem with Postgres' hash indexes is that no one has
worked on the hash-index code since Berkeley days (except for one or
two minor
On Wed, 24 Jul 2002, Daryl Herzmann wrote:
[lots of chopping and rearranging...]
> snet=# explain analyze select * from t2002_06 WHERE station = 'SAMI4';
> Seq Scan on t2002_06 (cost=0.00..35379.69)
> Total runtime: 2452.14 msec
>
> snet=# set enable_seqscan=off;
> snet=# explain analyze select *
24 de julho de 2002 12:46
> Para: Elielson Fontanezi
> Cc: pgsql-sql; pgsql-general
> Assunto: Re: RES: [SQL] Queries not using Index
>
>
> Hi!
>
> Thanks for the help. Please see my responses below.
>
> On Wed, 24 Jul 2002, Elielson Fontanezi wrote:
>
>
Hi!
Thanks for the help. Please see my responses below.
On Wed, 24 Jul 2002, Elielson Fontanezi wrote:
> What kind of index is t2002_06_station_idx?
snet=# select indexdef from pg_indexes where
indexname='t2002_06_station_idx';
indexdef
On Wed, 24 Jul 2002, Elielson Fontanezi wrote:
> Hi!
>
> What kind of index is t2002_06_station_idx?
> Have you done this SELECT command below, right?
>
> select * from t2002_06 WHERE station = 'SAMI4';
>
> This SELECT causes a sequention scan 'cause your index
> is not H
Hi!
What kind of index is t2002_06_station_idx?
Have you done this SELECT command below, right?
select * from t2002_06 WHERE station = 'SAMI4';
This SELECT causes a sequention scan 'cause your index
is not HASH type, but likely a BTREE one.
BTREE index is