Frank Mandarino wrote:
> 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 use
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.
Her
./fam
-- Forwarded message --
Date: Sun, 3 Oct 1999 19:50:37 -0400
From: Frank Mandarino <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: [GENERAL] btree index on a char(8) field
I am in the process of migrating a database from Postgres95 2.0 to
PostgreSQL 6.5.2 on a Debian 2.1 system.
I am in the process of migrating a database from Postgres95 2.0 to
PostgreSQL 6.5.2 on a Debian 2.1 system.
In a few of the tables, a char8 type field was used for the primary key,
so I converted them to type char(8). The tables also had a btree index
built on the primary key using char8_ops, wh
