Re: Strange issue with CREATE OPERATOR CLASS - Mailing list pgsql-hackers

From Josh Berkus
Subject Re: Strange issue with CREATE OPERATOR CLASS
Date
Msg-id 499362A5.7010605@agliodbs.com
Whole thread Raw
In response to Re: Strange issue with CREATE OPERATOR CLASS  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Strange issue with CREATE OPERATOR CLASS
List pgsql-hackers
Tom Lane wrote:
> Josh Berkus <josh@agliodbs.com> writes:
>> I've been working on some scripts (for pgfoundry) which help in 
>> "cleaning up" databases which have TSearch and other contrib modules 
>> installed to schema public.  However, I ran into this odd issue:
> 
>> ERROR:  btree operators must return boolean
> 
> Is that the actual error message?  The closest string I can find in 8.3
> or HEAD is "index operators must return boolean".

Oh!  Sorry, this is 8.2.12.  I can't reproduce it in 8.3 for obvious 
reasons, since there the TSearch stuff comes built-in.

> It seems possible that you could get an error like that as a result of
> something creating a shell operator and not filling it in afterwards,
> but if so I'd blame the earlier something; the worst that can be laid at
> CREATE OPERATOR CLASS's door is giving a less helpful error message than
> it could.  We really need to see a complete example of how to reproduce
> the problem before speculating about appropriate fixes.

Yeah, I'm trying to figure out the minimum test case; the one I have now 
contains proprietary client data, and *just* using tsearch2.sql doesn't 
produce the problem.

--Josh



pgsql-hackers by date:

Previous
From: Greg Smith
Date:
Subject: Re: A deprecation policy
Next
From: Tom Lane
Date:
Subject: Re: A deprecation policy