From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
---|---|
To: | Tatsuo Ishii <ishii(at)postgresql(dot)org> |
Cc: | alvherre(at)2ndquadrant(dot)com, Robert Haas <robertmhaas(at)gmail(dot)com>, tv(at)fuzzy(dot)cz, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: pgbench -f and vacuum |
Date: | 2015-02-10 08:12:40 |
Message-ID: | CAB7nPqTTHExR1Vf1BXkuNHenZ7WA5-zTf3ddNjByTkMPGzEV0A@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Feb 10, 2015 at 5:03 PM, Tatsuo Ishii wrote:
>> - The documentation misses some markups for pgbench and VACUUM and did
>> not respect the 80-character limit.
>
> I didn't realize that there's such a style guide. Although I think
> it's a good thing, I just want to know where such a guide is
> described.
That's self-learning based on the style of the other pages. I don't
recall if there are actually convention guidelines for the docs, the
only I know of being the coding convention here:
http://www.postgresql.org/docs/devel/static/source.html
Maybe we could have a section dedicated to that. Thoughts?
--
Michael
From | Date | Subject | |
---|---|---|---|
Next Message | Tatsuo Ishii | 2015-02-10 08:20:53 | Re: pgbench -f and vacuum |
Previous Message | Pavel Stehule | 2015-02-10 08:06:20 | Re: For cursors, there is FETCH and MOVE, why no TELL? |