Why should you care?

PostgresVerse enables pg_stat_statements on day one to find slow queries — one CREATE EXTENSION vs manual file copy.

See it live — copy this example

Run in pgAdmin or psql.

CREATE EXTENSION IF NOT EXISTS pg_stat_statements;

SELECT query, calls, mean_exec_time
FROM pg_stat_statements
WHERE dbid = (SELECT oid FROM pg_database WHERE datname = 'PostgresVerse')
ORDER BY mean_exec_time DESC
LIMIT 5;

What happened?

• pg_stat_statements tracks normalized query text and timing.
• Filter by PostgresVerse dbid.
• Top mean_exec_time reveals optimization targets.

Practice next

1. Add shared_preload_libraries = pg_stat_statements and restart (if needed).
2. CREATE EXTENSION in PostgresVerse.
3. Run app traffic or sample queries.
4. CREATE EXTENSION citext; use citext for case-insensitive email column.
5. CREATE EXTENSION pgcrypto; gen_random_uuid() alternative patterns.

Remember

Extensions versioned with CREATE EXTENSION. shared_preload_libraries needed for some modules. List available: SELECT * FROM pg_available_extensions;

PostgresVerse observability pack

SRE enables pg_stat_statements and pg_buffercache on staging before prod.

Outcome: Slow query review becomes weekly ritual with data.