# The missing PostgreSQL documentation

DevFeed: [The missing PostgreSQL documentation](<https://devfeed.tech/articles/the-missing-postgresql-documentation-41149.md>)

Original publisher: [Read original article](<https://www.craigkerstiens.com/2013/08/07/The-missing-PostgreSQL-documentation/>)

Author: Map

Published: 2013-08-07T20:55:56Z

Content type: opinion

Language: en

Sources: [Craig Kerstiens](<https://devfeed.tech/sources/craig-kerstiens.md>)

Topics: [PostgreSQL](<https://devfeed.tech/topics/postgresql.md>), [Documentation](<https://devfeed.tech/topics/documentation.md>), [Usability](<https://devfeed.tech/topics/usability.md>), [Tutorial](<https://devfeed.tech/topics/tutorial.md>)

Tags: [django](<https://devfeed.tech/tags/django.md>), [documentation](<https://devfeed.tech/tags/documentation.md>), [postgres](<https://devfeed.tech/tags/postgres.md>), [postgresql](<https://devfeed.tech/tags/postgresql.md>), [python](<https://devfeed.tech/tags/python.md>), [tutorial](<https://devfeed.tech/tags/tutorial.md>), [usability](<https://devfeed.tech/tags/usability.md>)

## AI overview

The article argues that PostgreSQL has strong reference documentation but lacks accessible onboarding materials and tailored guides. It suggests recreating the outdated tutorial and adding guides that help developers discover PostgreSQL features without already knowing their specialized names.

## Source excerpt

For a couple of years I've complained about the Postgres documentation and at the same time paraded it as one of the best sets of documentation I've encountered. In many ways the reason I veer towards Postgres as well as Python and Django is the quality of their documentation. If you need to find details about something its documented, and more importantly well and thoroughly documented. In large part I came to Python by happenstance through Django, and Postgres through happenstance of an employer. Yet, Django was very little of an accident. The Django Tutorial got me a large part of what I needed to know and more excited about development than I had been in some time. Python has done some work at adding docs to make this even better, sadly its still very much needed for PostgreSQL. Whats Missing in the Postgres Docs Theres a huge variety of types of documentation, off the top of my head theres: Reference docs (Postgres excels at this) Onboarding (Postgres tutorial huh?) Tailored guides (Postgres? I can haz? Nope... We don't understand....) Postgres is great if you know the name of what you're looking for, but if you don't you're entirely left in the dark. Understanding the power of Postgres Postgres is good enough at performance, good enough at usability, and awesome at how powerful and flexible it can be. But all of this is entirely lost if you have to know the esoteric name of what you're looking for. What the hell is an hstore... In so many ways KVstore makes infintely more sense. In the same sense PLV8, I have to know not only what PL stands for but V8 as well, versus the JavaScript extension for Postgres. I understand there are plenty of reasons why some of these things are the way they are, but its also limiting how great the broader perception is. Postgres externally is this hard to use DB, that well is just a database, versus giving developers a set of powerful and useful functions to make their lives better. The Solution Lets fix things, there are a ton of peopl