From: | Andreas Pflug <pgadmin(at)pse-consulting(dot)de> |
---|---|
To: | David Fetter <david(at)fetter(dot)org> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PG Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Comments on columns in the pg_catalog tables/views |
Date: | 2005-10-13 08:59:51 |
Message-ID: | 434E2207.2030909@pse-consulting.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
David Fetter wrote:
>>Dept of second thoughts: actually, perhaps see if you can generate
>>the pg_description entries from the C comments in the
>>include/catalog header files. There's already a strong motivation
>>to hold those to shorter-than-a-line length, whereas the column
>>descriptions in catalogs.sgml tend to run on a little longer, and
>>wouldn't format nicely in \dt+.
>
>
> My thought is that by the time somebody is doing \dt+ (or equivalent
> in other tools than psql) on a pg_catalog table or view, they need to
> see details and are at most slightly concerned about the formatting.
And not all tools have this formatting issue...
I like the long comments I can take from pg_settings, enabling pgAdmin
to deliver precise information on each config option.
Regards,
Andreas
From | Date | Subject | |
---|---|---|---|
Next Message | Charles Wegrzyn | 2005-10-13 13:24:27 | BUG #1962: ECPG and VARCHAR |
Previous Message | Kevin Grittner | 2005-10-13 06:57:31 | Re: A costing analysis tool |