Re: pgstat documentation tables - Mailing list pgsql-hackers

From Magnus Hagander
Subject Re: pgstat documentation tables
Date
Msg-id CABUevEy2Bm=qHMORfOA0g7qozm3V3pS-+2UN17N+j9o6boEZbA@mail.gmail.com
Whole thread Raw
In response to Re: pgstat documentation tables  (Greg Smith <greg@2ndQuadrant.com>)
List pgsql-hackers
On Sun, Jan 15, 2012 at 10:35, Greg Smith <greg@2ndquadrant.com> wrote:
> On 01/15/2012 03:51 AM, Magnus Hagander wrote:
>>
>> I'd like to turn that into one table for each view, with two columns,
>> one being the name the other one being the description. That'll also
>> make it possible to expand on the descriptions without making it
>> completley unreadable, should we want to.
>
>
> Scott Mead's pg_stat_activity refactoring patch already was forced toward
> doing something similar for its documentation to be readable (maybe exactly
> the same as you were thinking, can't tell because my SGML-fu is weak) .  I
> feel doing this for every view in there is inevitable, just a matter of when
> to bite on the problem.  This whole section is barely usable in its current
> form.  I strongly hope the pg_stat_activity patch goes in, which will be
> close to a compelling event to motivate fixing the rest of them in a similar
> way.  I would advocate leading with that one until it seems right, then
> adopting the same style of reorg to the rest until they're all converted.

Yes, the pg_stat_activity patch will make it more important - but I
want to do it for *all* of them...

I'll be happy to do the mechanical work on turning them into table,
but yes, I was planning to look at the pg_stat_activity patch first
all along :)

--
 Magnus Hagander
 Me: http://www.hagander.net/
 Work: http://www.redpill-linpro.com/


pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: lots of unused variable warnings in assert-free builds
Next
From: Magnus Hagander
Date:
Subject: Re: Patch to allow users to kill their own queries