Re: Comments on columns in the pg_catalog tables/views - Mailing list pgsql-hackers

From Christopher Kings-Lynne
Subject Re: Comments on columns in the pg_catalog tables/views
Date
Msg-id 434DC354.1080209@familyhealth.com.au
Whole thread Raw
In response to Comments on columns in the pg_catalog tables/views  (David Fetter <david@fetter.org>)
List pgsql-hackers
Yes for the love of god do it :D

David Fetter wrote:
> Folks,
> 
> Before I dive into this, is there some reason why the pg_catalog.*
> tables/views should not have comments that match the descriptions in
> the docs?  I can see where this could cause some maintenance issues,
> and those probably need to be addressed, but it sure would be nice if
> \d+ pg_depend pulled up something like:
> 
>           Table "pg_catalog.pg_depend"
>    Column    |  Type   | Modifiers | Description
> -------------+---------+-----------+-------------
>  classid     | oid     | not null  | The OID of the system catalog the dependent object is in
>  objid       | oid     | not null  | The OID of the specific dependent object
>  objsubid    | integer | not null  |  For a table column, this is the column number (the objid and classid refer to
thetable itself). For all other object types, this column is zero.
 
>  refclassid  | oid     | not null  | The OID of the system catalog the referenced object is in
>  refobjid    | oid     | not null  | The OID of the specific referenced object
>  refobjsubid | integer | not null  |  For a table column, this is the column number (the refobjid and refclassid
referto the table itself). For all other object types, this column is zero.
 
>  deptype     | "char"  | not null  |  A code defining the specific semantics of this dependency relationship; see
text.
> 
> Cheers,
> D



pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: A costing analysis tool
Next
From: Bruce Momjian
Date:
Subject: Re: [COMMITTERS] pgsql: Do all accesses to shared buffer headers through