On Tue, 11 Jan 2000, admin wrote:
> > > I'm trying to use an index on a varchar(32) field, but explain keeps
> > > retuning a sequential scan. This is my table and index:
> >
> > I had a similar problem last year when trying to use an index on a
> > char(8) field. Two solutions worked for me:
r when trying to use an index on a
char(8) field. Two solutions worked for me: 1) use "bpchar_ops", and
2) leave out the operator class altogether.
I have attached the response from Gene Selkov, Jr. which suggested that
I let PostgreSQL pick the operator class.
Perhaps leaving out t
./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
