From: | Josh Berkus <josh(at)agliodbs(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Strange issue with CREATE OPERATOR CLASS |
Date: | 2009-02-11 23:43:33 |
Message-ID: | 499362A5.7010605@agliodbs.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote:
> Josh Berkus <josh(at)agliodbs(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2009-02-11 23:56:54 | Re: A deprecation policy |
Previous Message | Greg Smith | 2009-02-11 23:31:49 | Re: A deprecation policy |