On Fri, Feb 12, 2010 at 9:10 PM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> On Fri, Feb 12, 2010 at 7:30 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> Maybe a more general idea would be to invent "categories" of opclass
>> members, where the only existing category is "index search qualifier",
>> and these new knngist thingies are another, and maybe plus and minus for
>> window function ranges are a third. But I'm not sure what you do if one
>> operator can be in more than one category.
> Well, if you were willing to change pg_amop so that the key was
> (amopfamily, amoplefttype, amoprighttype, amopcategory) rather than
> just (amopfamily, amoplefttype, amoprighttype), the issue of what to
> do if an operator can be in more than one category becomes moot. You
> just specify the operator more than once if need be.
Except I'm full of it, because amopstrategy is in there too. Hmm.
And that's unfortunate because the syscache machinery is limited to
four columns as lookup keys.
This is a bit ugly, but one idea that occurs to me is to change
amopstrategy from int16 to int32. Internally, we'll treat the low 16
bits as the strategy number and the high 16 bits as the strategy
category, with strategy category 0 being "index search qualifier".
In response to
pgsql-hackers by date
|Next:||From: Tom Lane||Date: 2010-02-13 02:31:56|
|Subject: Re: Writeable CTEs and empty relations |
|Previous:||From: Robert Haas||Date: 2010-02-13 02:14:47|
|Subject: Re: Package namespace and Safe init cleanup for plperl [PATCH]|