From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
Cc: | Martijn van Oosterhout <kleptog(at)svana(dot)org>, Gregory Stark <stark(at)enterprisedb(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Operator class group proposal |
Date: | 2006-12-16 20:14:14 |
Message-ID: | 7598.1166300054@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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
OID
opfamid access method OID
opfname family name
opfnamespace family namespace
opfowner 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
From | Date | Subject | |
---|---|---|---|
Next Message | Pavel Stehule | 2006-12-16 21:38:40 | info from prepared plan? |
Previous Message | Tom Lane | 2006-12-16 19:53:55 | Re: Operator class group proposal |