Re: [GENERAL] btree index on a char(8) field (fwd) - Mailing list pgsql-general

From Frank Mandarino
Subject Re: [GENERAL] btree index on a char(8) field (fwd)
Date
Msg-id 99Oct6.234802edt.115201@sky.risca.com
Whole thread Raw
In response to Re: [GENERAL] btree index on a char(8) field (fwd)  (Herouth Maoz <herouth@oumail.openu.ac.il>)
Responses Re: [GENERAL] btree index on a char(8) field (fwd)
List pgsql-general
Hermouth,

Thank you so much for your reply!  You were exactly right.  I re-created
the index with bpchar_ops, and explain now outputs:

    Index Scan using ven_code_idx on vendor  (cost=2.05 rows=2 width=36)

instead of

    Seq Scan on vendor  (cost=738.86 rows=2 width=36)

Queries are obviously much faster now.

I am unable to find any reference to bpchar_ops in the the documentation
or the General and SQL mailing list archives.  Can you tell me where I
could find out more about what "_ops" are available and what they all
mean?

Thanks again,
../fam
--
Frank A. Mandarino
fam@risca.com


On Wed, 6 Oct 1999, Herouth Maoz wrote:

> At 15:30 +0200 on 06/10/1999, Frank Mandarino wrote:
>
>
> > main=> create index ven_code_idx on vendor using btree (ven_code char_ops);
> > CREATE
>
> I didn't have time to check this, but the problem may be caused by the
> incorrect ops you are using. For char(N) it should be bpchar_ops, not
> char_ops.
>
> Herouth
>
> --
> Herouth Maoz, Internet developer.
> Open University of Israel - Telem project
> http://telem.openu.ac.il/~herutma
>
>
>
> ************
>



pgsql-general by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: PostgreSQL vs Mysql comparison
Next
From: Kaare Rasmussen
Date:
Subject: [GENERAL] Re: PostgreSQL vs Mysql comparison