Skip site navigation (1) Skip section navigation (2)

a btree strategy hosed in 6.4.BETA1 and in current snapshot

From: "Gene Selkov, Jr(dot)" <selkovjr(at)mcs(dot)anl(dot)gov>
To: pgsql-hackers(at)postgresql(dot)org
Subject: a btree strategy hosed in 6.4.BETA1 and in current snapshot
Date: 1998-10-10 20:06:16
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
Hi hackers,

I have trouble understanding the message I got in response to CREATE INDEX:

CREATE INDEX ecix ON ec USING btree ( ec ec_code_ops );
ERROR:  RelationInvokeStrategy: cannot evaluate strategy 5

The strategy in question is defined as:

INSERT INTO pg_amop (amopid, amopclaid, amopopr, amopstrategy, 
                     amopselect, amopnpages)
   SELECT am.oid, opcl.oid, c.opoid, 5,
        'btreesel'::regproc, 'btreenpage'::regproc
   FROM pg_am am, pg_opclass opcl, ec_code_ops_tmp c
   WHERE amname = 'btree' and opcname = 'ec_code_ops' 
      and c.oprname = '>';

where ec_code_ops_tmp is the result of:

SELECT o.oid AS opoid, o.oprname
INTO TABLE ec_code_ops_tmp
FROM pg_operator o, pg_type t
WHERE o.oprleft = t.oid and o.oprright = t.oid
   and t.typname = 'ec_code';

But I can evaluate this function as an operator without problems:

emp=> select * from test_ec where ec > '5';
(4 rows)

This did not happen to me in older versions, including 6.3.2-release. I am wondering whether something changed in btree after 6.3.2, and how do I accomodate my extensions if it did.

Thank you,


(I would appreciate a direct reply, as I am not a member of the hackers list)

pgsql-hackers by date

Next:From: Oliver ElphickDate: 1998-10-10 22:06:22
Subject: Re: [HACKERS] backslash in psql output
Previous:From: Tom Ivar HelbekkmoDate: 1998-10-10 18:14:51
Subject: Re: [HACKERS] Open 6.4 items

Privacy Policy | About PostgreSQL
Copyright © 1996-2018 The PostgreSQL Global Development Group