Robert Haas looks
at the advantages and disadvantages of how documentation for PostgreSQL
is written.

The strengths of this process are also its weaknesses. A developer
is, by definition, someone who spends the majority of their time
doing development, which is to say writing code. Updating the
documentation becomes a task that must be completed so that the
code one has written can get committed so that one can move on to
the next project and write some more code. If a change to the
documentation would be beneficial but is unrelated to any
particular patch, it’s not likely to get done.

The results are, in a certain sense, pretty comical.

Source: LWN.net – Haas: The PostgreSQL Documentation and the Limitations of Community