TL;DR verdict
Use the official PostgreSQL tutorial as the versioned introduction, PostgreSQL Exercises for repeated SQL practice, and Crunchy Data tutorials for selected applied topics. This is an editorial sequence for a defined curriculum, not a universal course ranking.
The path is incomplete until you can inspect a query plan, explain an index tradeoff, preserve a transaction invariant, and restore a database. Those tasks are a CourseFacts editorial lab, not a completion guarantee from any source.
Key takeaways
- PostgreSQL 18.6, released August 13, 2026, was the current point release named by the official versioning page at access time; the current tutorial is PostgreSQL 18.
- The three learning resources were publicly reachable at access time. Commercial terms require separate verification for any paid follow-on resource.
- Ratings and enrollment not compared: this is a scope-based evaluation of documentation, exercises, and applied tutorials.
- Keep a clear core PostgreSQL versus provider or extension boundary, and record exact version details with every command or result.
- Treat query and restore results as a reproducible local measurement with the version and configuration recorded, not as a general benchmark.
At-a-glance learning sequence
| Step | Resource | Source-supported scope | Add yourself |
|---|---|---|---|
| 1 | PostgreSQL 18 Tutorial | Introductory relational, SQL, and PostgreSQL concepts | A local database, notes, and version checks |
| 2 | PostgreSQL Exercises | Interactive SQL practice | Query-plan inspection and representative data |
| 3 | Crunchy Data Postgres Tutorials | Applied provider tutorials | Exact version checks and separation from core behavior |
| 4 | CourseFacts editorial lab | A structured practice plan | Constraints, concurrency, migration, plan analysis, backup, and restore evidence |
Evidence cards
Official PostgreSQL tutorial
The official tutorial is tied to the current documentation line and provides the canonical starting vocabulary for relational concepts, SQL, and PostgreSQL-specific features. The current tutorial is PostgreSQL 18. Recheck current version information before following commands because major and minor releases, packaging, and extension compatibility can differ.
PostgreSQL Exercises
PostgreSQL Exercises provides interactive practice for retrieval, joins, aggregation, dates, and recursive queries. Use it after an introductory pass to expose gaps in query formulation. It does not establish administration, migration, recovery, or production-operating competence on its own.
Crunchy Data tutorials
Crunchy Data publishes applied PostgreSQL tutorials. Select a tutorial for a concrete gap, then identify provider context, extension use, managed-service assumptions, and the PostgreSQL version before copying commands into another environment.
Curriculum beyond SQL syntax
A practical PostgreSQL path should include:
- data types, keys, constraints, and migration safety;
- joins, subqueries, CTEs, window functions, and transaction boundaries;
EXPLAIN (ANALYZE, BUFFERS)on representative data;- index selectivity plus write and storage costs;
- locks, isolation, deadlocks, and retry behavior;
- roles, privileges, connection limits, logs, backup, and restore;
- explicit labeling for extensions and managed-service features.
This combines source-supported scope with an editorial practice standard. The sources identify current learning materials; they do not promise that every operational topic is taught.
CourseFacts editorial lab
Build a small transactional system with one enforceable invariant. Seed enough data to make plan choices visible, then complete this sequence:
- Save a baseline query, raw plan, schema, data characteristics, server version, and configuration.
- Make one index or query change and rerun correctness checks plus repeated measurements.
- Open two sessions and record one lock, concurrent update, or isolation case.
- Apply a backward-compatible migration and test old and new behavior.
- Create a least-privilege role and prove a forbidden action fails.
- Back up the database, restore into a clean environment, and run integrity checks.
A performance statement from this lab is a reproducible local measurement only when it includes the exact version and configuration, schema, data distribution, hardware, query, raw plan, repetitions, and correctness checks. It is no general benchmark for PostgreSQL or another environment.
The project evidence is learner-produced. It carries no career or salary guarantee; it is an artifact a reviewer can inspect.
Methodology
The evidence here comes from the official PostgreSQL tutorial and versioning page, PostgreSQL Exercises, and Crunchy Data tutorials. The learning order moves from documented concepts to deliberate SQL practice, applied follow-on material, and then an editorial operations lab.
We did not use reviews, enrollment, provider popularity, or unscoped performance claims. We also separated core PostgreSQL from extensions, client libraries, operating-system packaging, provider tutorials, and managed-service behavior.
Source-backed FAQ
Is the official tutorial enough by itself?
It is an introductory foundation. Add exercises plus a project that tests plans, transactions, migration, permissions, backup, and restore.
Why include PostgreSQL Exercises?
It converts introductory SQL concepts into repeated query practice. Treat it as one layer rather than proof of broader database-operating competence.
How should I evaluate an index change?
Record the exact PostgreSQL version, configuration, schema, data distribution, hardware, query, raw plans, repeated timings, and correctness checks. A single local plan does not establish a general result.
Are these resources permanently free or maintained?
The pages were reachable on 2026-08-23. That dated result does not promise future access, support, maintenance, or version compatibility. Verify commercial follow-ons separately.
Source Notes
The official tutorial and versioning page, PostgreSQL Exercises, and Crunchy Data tutorials were accessed 2026-08-23. Their reachability is point-in-time. Recheck current version, future URLs, maintenance, support, and environment compatibility before relying on a command sequence.
- PostgreSQL: PostgreSQL 18 Tutorial and Versioning Policy.
- PostgreSQL Exercises: interactive exercises.
- Crunchy Data: Postgres Tutorials.