PostgreSQL ecosystem preview

Postgres is more than a single binary: extensions, hosting providers, GUI clients, and migration tools form an ecosystem you will touch in real projects.

Extensions (preview)

-- See installed extensions
SELECT name, default_version, installed_version
FROM pg_available_extensions
WHERE name IN ('postgis', 'citext', 'pg_trgm')
ORDER BY name;

CREATE EXTENSION loads optional modules into a database—covered later in this track.

Practice: Copy SQL into psql, a local PostgreSQL server, or DB Fiddle (PostgreSQL dialect). Compare output with the lesson.

Tooling landscape

• psql — official interactive CLI
• pgAdmin / DBeaver — GUI explorers
• Managed Postgres — RDS, Cloud SQL, Supabase, Neon
• App drivers — psycopg (Python), JDBC, Node pg

Django and Postgres

Django treats PostgreSQL as a first-class production database—JSONField maps to JSONB, ArrayField to arrays, and migrations emit Postgres-specific DDL when needed.

Important interview questions and answers

1. Q: What is PostGIS?
   A: Extension adding geographic types and spatial queries—teaser later in this track.
2. Q: Why managed Postgres?
   A: Automated backups, patching, and HA—teams trade ops burden for vendor SLAs.

Self-check

1. Name two ways to connect to Postgres besides psql.
2. What catalog lists available extensions?

Tip: Bookmark your cloud provider's allowed extension list before designing on PostGIS or pgvector.