On 09/19/2018 10:54 AM, Tom Lane wrote: > Joe Conway <m...@joeconway.com> writes: >> * I do believe aclitemeq() has utility outside internal purposes. > > Our normal policy is that we do not document functions that are meant to > be invoked through operators. The \df output saying that is sufficient:
<snip> > I would strongly object to ignoring that policy in just one place. Ok, fair enough. > Actually, it appears that most of these functions have associated > operators: > > # select oid::regoperator, oprcode from pg_operator where oprright = > 'aclitem'::regtype; > oid | oprcode > -----------------------+------------- > +(aclitem[],aclitem) | aclinsert > -(aclitem[],aclitem) | aclremove > @>(aclitem[],aclitem) | aclcontains > =(aclitem,aclitem) | aclitemeq > ~(aclitem[],aclitem) | aclcontains > (5 rows) > > So maybe what we really need is a table of operators not functions. Good idea -- I will take a look at that. > However, I don't object to documenting any function that has its > own pg_description string. Ok. Joe -- Crunchy Data - http://crunchydata.com PostgreSQL Support for Secure Enterprises Consulting, Training, & Open Source Development
signature.asc
Description: OpenPGP digital signature
