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

From Tom Lane
Subject Re: [HACKERS] Re: [PATCHES] COMMENT ON patch
Date
Msg-id 17750.940863733@sss.pgh.pa.us
Whole thread Raw
In response to Re: [HACKERS] Re: [PATCHES] COMMENT ON patch  (Peter Eisentraut <e99re41@DoCS.UU.SE>)
Responses Re: [HACKERS] Re: [PATCHES] COMMENT ON patch  (Bruce Momjian <maillist@candle.pha.pa.us>)
List pgsql-hackers
Peter Eisentraut <e99re41@DoCS.UU.SE> writes:
> On Sun, 24 Oct 1999, Mike Mascari wrote:
>> 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.

Two functions?  An operator only has one underlying function.
(Aggregates have as many as three though.)

> Try \do and see for yourself. The fix should be rather simple but I'm not
> sure where those descriptions are generated actually.

The default contents of pg_description come from the DESCR() macros in
include/catalog/*.h.  It looks like only pg_proc and pg_type have any
useful info in them in the current state of the source.  I'm guessing
that psql's \do actually looks for a description attached to the
underlying function, rather than one attached to the operator.
        regards, tom lane


pgsql-hackers by date:

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