Comments on columns in the pg_catalog tables/views

From: David Fetter <david(at)fetter(dot)org>
To: PG Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Comments on columns in the pg_catalog tables/views
Date: 2005-10-12 19:54:19
Message-ID: 20051012195419.GC24235@fetter.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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 the table 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 refer to 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
--
David Fetter david(at)fetter(dot)org http://fetter.org/
phone: +1 510 893 6100 mobile: +1 415 235 3778

Remember to vote!

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Martijn van Oosterhout 2005-10-12 21:00:38 Re: database vacuum from cron hanging
Previous Message Kevin Grittner 2005-10-12 19:54:15 Are cost estimates based on asserts?