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

From Tom Lane
Subject Re: Operator class group proposal
Date
Msg-id 7598.1166300054@sss.pgh.pa.us
Whole thread Raw
In response to Re: Operator class group proposal  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Operator class group proposal  ("Zeugswetter Andreas ADI SD" <ZeugswetterA@spardat.at>)
List pgsql-hackers
>>>> "Operator family" seems like it might be a good choice.
>>> I like this one more than opcluster. opfamily has a good ring to it also.
>> +1 on opfamily.
> Done, unless anyone really doesn't like it.

So I started revising my notes on what to change the catalog structure
to, and immediately came up with

pg_opfamily
OIDopfamid            access method OIDopfname            family nameopfnamespace        family namespaceopfowner
owner's OID
 

But "opfamid" is a really unfortunate name, because it looks way too
much like it's supposed to be the ID of the family itself, rather than
of the index AM it's associated with.

I'm thinking of changing it to "opfmethod", and similarly rename
pg_opclass.opcamid to opcmethod.  That might break a few bits of code
that needn't be broken, but on the whole this patch will whack the
opclass-related catalogs around enough that most code looking at them
will need fixes anyway.

Comments?
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Operator class group proposal
Next
From: "Pavel Stehule"
Date:
Subject: info from prepared plan?