Re: Indexing new type ........ - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Indexing new type ........
Date
Msg-id 2306.982250276@sss.pgh.pa.us
Whole thread Raw
In response to Indexing new type ........  (<pejac@altern.org>)
List pgsql-hackers
<pejac@altern.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


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Shouldn't non-MULTIBYTE backend refuse to start in MB database?
Next
From: Peter Eisentraut
Date:
Subject: Re: Shouldn't non-MULTIBYTE backend refuse to start in MB database?