PostgreSQL interview question · Most asked
Which PostgreSQL extensions do you find most useful?
Summary
pg_stat_statements (query performance statistics), pg_trgm (fuzzy text search), PostGIS (geospatial), pgvector (vector similarity search for embeddings), citext (case-insensitive text), pgcrypto, pg_partman (partition management) and auto_explain (log plans of slow queries).
Longer Answer
Extensions are a major reason teams choose PostgreSQL: they add types, index methods and functions without leaving the database. On managed services you can only use the extensions the provider supports, so check before designing around one. Extensions also need upgrading alongside major versions (ALTER EXTENSION ... UPDATE).
Key Points
- pg_stat_statements is essential.
- PostGIS, pgvector, pg_trgm, citext.
- Managed services limit available extensions.
More most-asked PostgreSQL questions
- How does MVCC work in PostgreSQL?
- JSON or JSONB in PostgreSQL, and how do you index JSONB?
- What does VACUUM do, and how does autovacuum work?
- How do you read EXPLAIN ANALYZE output in PostgreSQL?
- What isolation levels does PostgreSQL provide, and how do they behave?
- What index types does PostgreSQL support, and when do you use each?
- Which schema changes take heavy locks in PostgreSQL, and how do you avoid outages during migrations?
- Why do PostgreSQL deployments need connection pooling, and how do PgBouncer's modes differ?