From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
---|---|
To: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, 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-11 02:36:11 |
Message-ID: | 54DAC01B.6020608@gmx.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 2/10/15 3:12 AM, Michael Paquier wrote:
> 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?
We have http://www.postgresql.org/docs/devel/static/docguide-style.html,
although that doesn't cover formatting. For that we have .dir-locals.el:
(sgml-mode . ((fill-column . 78)
(indent-tabs-mode . nil))))
;-)
Feel free to improve that.
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2015-02-11 02:38:26 | Re: reducing our reliance on MD5 |
Previous Message | Tom Lane | 2015-02-11 02:30:37 | Re: reducing our reliance on MD5 |