One example is "CONF" [1], a website that provides:

a) Detailed documentation about every postgresql.conf configuration parameter (in several languages), for Postgres version 9.1-current. Includes recommendations, comments and links to relevant threads in SO and PostgreSQL Hacker's mailing list relevant to every parameter.

b) A tool to manage postgresql.conf configuration, with tuning guides, the option to store your configs and download in multiple formats, and an open API behind it.

All website is 100% free for the Postgres Community. Disclosure: my company is behind this project.

Edit: minor edits.

[1]: https://postgresqlco.nf/

I think this is just copied from original PG docs: https://www.postgresql.org/docs/7.2/locking-tables.html

That's a _very_ outdated document. Current version is https://www.postgresql.org/docs/current/explicit-locking.htm...

yeah, my link somehow was first in google search..

It's a common issue with PG documentation, google often leads you to documentation for old versions (or it's an indication that these versions are actually still highly relevant)

Fortunately PG is very good at keeping the documentation structure the same between major versions and provides crosslinks to the proper documentation for all PG versions on (almost?) all pages