Re: Indexing new type ........

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pejac(at)altern(dot)org
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Indexing new type ........
Date: 2001-02-15 15:17:56
Message-ID: 2306.982250276@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

<pejac(at)altern(dot)org> writes:
> So i use the following query in order to have default operator:
> INSERT INTO pg_opclass(opcname,opcdeftype) select 'ean13_ops',oid
> from pg_type where typname = 'ean13' ;
> So the new error with postgresql when i try to create an index
> on my new type is : opclass "ean13" not supported by
> access method btree

You need some entries in pg_amop and pg_amproc as well. See the section
on "interfacing extensions to indices" in the Programmer's Guide.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2001-02-15 17:41:43 Re: Shouldn't non-MULTIBYTE backend refuse to start in MB database?
Previous Message Tom Lane 2001-02-15 15:04:44 Re: Shouldn't non-MULTIBYTE backend refuse to start in MB database?