| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | Mike Mascari <mascarim(at)yahoo(dot)com>, pgsql-hackers(at)postgreSQL(dot)org |
| Subject: | Re: [HACKERS] Re: [PATCHES] COMMENT ON patch |
| Date: | 1999-10-25 15:02:13 |
| Message-ID: | 17750.940863733@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Peter Eisentraut <e99re41(at)DoCS(dot)UU(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stéphane FILLON | 1999-10-25 17:11:08 | RE: mv backend/port ../../ |
| Previous Message | Nguyen, Thuan X | 1999-10-25 13:38:38 |