On 08/06/14 05:03, Kevin Grittner wrote:
[...]
> I found it hard to decide how far to go in the docs versus the Wiki
> page. Any suggestions or suggested patches welcome.
[...]
> I know this is subjective, but that seems to me a little too much in
> an academic style for the docs. In the Wiki page examples I tried to
> use a style more accessible to DBAs and application programmers.
> Don't get me wrong, I found various papers by Alan Fekete and others
> very valuable while working on the feature, but they are often geared
> more toward those developing such features than those using them. That
> said, I know I'm not the best word-smith in the community, and would
> very much welcome suggestions from others on the best way to cover
> this. -- Kevin Grittner EDB: http://www.enterprisedb.com The
> Enterprise PostgreSQL Company
I know that I first look at the docs & seldom look at the Wiki - in fact
it was only recently that I became aware of the Wiki, and it is still
not the first thing I think of when I want to know something, and I
often forget it exists. I suspect many people are like me in this!
Also the docs have a more authoritative air, and probably automatically
assumed to be more up-to-date and relevant to the version of Postgres used.
So I suggest that the docs should have an appropriate coverage of such
topics, possibly mostly in an appendix with brief references in affected
parts of the main docs) if it does not quite fit into the rest of the
documentation (affects many different features, so no one place in the
main docs is appropriate - or too detailed, or too much). Also links to
the Wiki, and to the more academic papers, could be provided for the
really keen.
Cheers,
Gavin
