Re: [HACKERS] Re: [PATCHES] COMMENT ON patch - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: [HACKERS] Re: [PATCHES] COMMENT ON patch
Date
Msg-id Pine.GSO.4.02A.9910251042430.8338-100000@Krabba.DoCS.UU.SE
Whole thread Raw
In response to Re: [HACKERS] Re: [PATCHES] COMMENT ON patch  (Mike Mascari <mascarim@yahoo.com>)
Responses Re: [HACKERS] Re: [PATCHES] COMMENT ON patch  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Sun, 24 Oct 1999, Mike Mascari wrote:

> Hmm, this is where I'm getting the oid's:
> 
> DATABASE -- pg_database
> INDEX -- pg_class
> RULE -- pg_rewrite
> SEQUENCE -- pg_class
> TABLE -- pg_class
> TYPE -- pg_type
> VIEW -- pg_class
> COLUMN -- pg_attribute
> AGGREGATE -- pg_aggregate
> FUNCTION -- pg_proc
> OPERATOR -- pg_operator
> TRIGGER -- pg_trigger
> 
> So in the example you gave above, you could put a comment
> on each of the two functions which compose the operator
> and a command on the operator itself.

Very nice, BUT: In the old psql the assumption was that operator comments
are keyed on the underlying function(s?). Since a lot of operators seem to
have comments on them by default, one would have to change this somehow.
Try \do and see for yourself. The fix should be rather simple but I'm not
sure where those descriptions are generated actually.
-Peter

-- 
Peter Eisentraut                  Sernanders vaeg 10:115
peter_e@gmx.net                   75262 Uppsala
http://yi.org/peter-e/            Sweden



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [HACKERS] Re: [PATCHES] COMMENT ON patch
Next
From: "Nguyen, Thuan X"
Date:
Subject: