Re: Operator class group proposal - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Operator class group proposal
Date
Msg-id 12615.1166049757@sss.pgh.pa.us
Whole thread Raw
In response to Operator class group proposal  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Operator class group proposal  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
I wrote:
> We further require that any given opclass be a member of at most one class
> group (this simplifies matters, and there isn't any application I can see
> for one opclass being in more than one group), and that a class group
> contain at most one opclass for a given datatype (ditto).

BTW, I forgot to mention one of the motivations for that last
restriction: I'm thinking it would be convenient to allow index
declarations to accept either an opclass name or a class group name.
Thus you could say "pattern_ops" instead of being specific about
"varchar_pattern_ops" or "text_pattern_ops".  Not sure whether
there's a need to worry about name collisions ...
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Operator class group proposal
Next
From: Tatsuo Ishii
Date:
Subject: Re: pg_standby and build farm