Re: [HACKERS] Re: [PATCHES] COMMENT ON patch

From: Peter Eisentraut <e99re41(at)DoCS(dot)UU(dot)SE>
To: Mike Mascari <mascarim(at)yahoo(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: [HACKERS] Re: [PATCHES] COMMENT ON patch
Date: 1999-10-25 08:49:41
Message-ID: Pine.GSO.4.02A.9910251042430.8338-100000@Krabba.DoCS.UU.SE
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(at)gmx(dot)net 75262 Uppsala
http://yi.org/peter-e/ Sweden

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Ben Bennett 1999-10-25 11:39:02 Re: [HACKERS] Logging - events supported
Previous Message Tom Lane 1999-10-25 05:36:33 Re: [HACKERS] Re: [PATCHES] COMMENT ON patch