From: | Magnus Hagander <magnus(at)hagander(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Greg Smith <greg(at)2ndquadrant(dot)com>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us> |
Subject: | Re: pgstat documentation tables |
Date: | 2012-02-08 06:17:23 |
Message-ID: | CABUevEwosmc=7TPOrtXbyy-c2v5kq-UFeZnjahbEzFAkCwjz4w@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Feb 8, 2012 5:32 AM, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> Bruce Momjian <bruce(at)momjian(dot)us> writes:
> > How do people feel about pulling text out of the SGML docs and loading
> > it into the database as table and column comments?
>
> I'm not thrilled by that proposal. The length limits on comments are
> very much shorter than what is sensible to use in catalogs.sgml (at
> least if you want the comments to look passable in \d displays). And
> I don't want people trying to serve two different use-cases when they
> write those.
Yes, I'd rather see longer than shorter descriptions in the docs, and this
would turn that backwards...
>
> Perhaps it'd work to pull column comments from the C header files
> --- any same-line comment in catalog/pg_*.h is probably short enough to
> serve this purpose usefully.
That could work a lot better..
/Magnus
From | Date | Subject | |
---|---|---|---|
Next Message | Chetan Suttraway | 2012-02-08 06:39:34 | Re: patch for preventing the specification of conflicting transaction read/write options |
Previous Message | Shigeru Hanada | 2012-02-08 05:44:13 | Re: Speed dblink using alternate libpq tuple storage |