Re: machine-parseable object descriptions - Mailing list pgsql-hackers

From Tom Lane
Subject Re: machine-parseable object descriptions
Date
Msg-id 1698.1363788706@sss.pgh.pa.us
Whole thread Raw
In response to Re: machine-parseable object descriptions  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Responses Re: machine-parseable object descriptions  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List pgsql-hackers
Alvaro Herrera <alvherre@2ndquadrant.com> writes:
> The new identity column is amazingly verbose on things like pg_amproc entries:

>  10650 | 1 (pg_catalog.point, pg_catalog.point) of pg_catalog.point_ops for gist:
pg_catalog.gist_point_consistent(pg_catalog.internal,pg_catalog.point,integer,pg_catalog.oid,pg_catalog.internal)

Uh ... isn't that confusing the *identity* of the pg_amproc entry with
its *content*?  I would say that the function reference doesn't belong
there.  You do need the rest.  I would also suggest that you prepend
the word "function" (or "operator" for pg_amop), so that it reads like
"function 1 (typename, typename) of opfamilyname for amname".
        regards, tom lane



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: A few string fixed
Next
From: Magnus Hagander
Date:
Subject: Materialized views vs event triggers missing docs?