From: | Frank Mandarino <fam(at)risca(dot)com> |
---|---|
To: | "Gene Selkov, Jr(dot)" <selkovjr(at)mcs(dot)anl(dot)gov> |
Cc: | pgsql-general(at)postgreSQL(dot)org |
Subject: | Re: [GENERAL] btree index on a char(8) field (fwd) |
Date: | 1999-10-07 11:53:10 |
Message-ID: | 99Oct7.075338edt.115202@sky.risca.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Gene,
Thanks for your response.
I knew from the programming documentation that the opclass was optional.
I'm pretty sure, although I will check again tonight, that I tried
creating the index without specifying the opclass, but I found that the
index was still not used in my example query.
Do you know which opclass that Postgres should choose for char(8) types?
Regards,
../fam
--
Frank A. Mandarino
fam(at)risca(dot)com
On Thu, 7 Oct 1999, Gene Selkov, Jr. wrote:
>
> My comment:
>
> The deficiency of the docs in regards to operator classes probably
> results from the fact that no one is asking about those. The opclass
> parameter in CREATE INDEX is no longer required (Herouth has been
> around long enough to recall the times when it was).
>
> As you have just witnessed, in a standard situation, you are better
> off without knowing about it -- postgres will pick the right opclass
> for you. That will not happen, however, when the values you want to
> index are of a custom type, or when a built-in type does not have an
> opclass of its own (as is the case with the point type). Also, you
> need this option to override the default opclass for those types that
> can work with multiple opclasses (which is what you attempted to
> achieve).
>
> Will anyone with a solid knowledge of the type system want to augment
> the existing docs?
>
> --Gene
>
> ************
>
From | Date | Subject | |
---|---|---|---|
Next Message | Karl DeBisschop | 1999-10-07 13:06:09 | Re: [GENERAL] what does this mean - pg_psort.1922.0 in database directory? |
Previous Message | Andrew Higgs | 1999-10-07 11:25:21 | UNSUBSCRIBE |