Admin for PostgreSQLs
Admin covers configuring and securing a PostgreSQL server. postgresql.conf sets memory and connection parameters such as shared_buffers and max_connections, pg_hba.conf decides who may connect from where, and roles with GRANT control permissions. Connection pooling with PgBouncer protects the server from too many clients.
Stage: Administration · Part of the PostgreSQL roadmap · Last reviewed 19 November 2026
What to learn in Admin
- Edit postgresql.conf and reload the server without a restart
- Write pg_hba.conf rules that restrict hosts and require password authentication
- Create roles with least-privilege GRANT statements
- Enable TLS for client connections
- Place PgBouncer in front of the database to pool connections
Admin interview questions
What does pg_hba.conf control?
It is the client authentication file. Each line matches a connection type, database, user and address to an authentication method such as scram-sha-256 or reject. Rules are read top to bottom and the first match applies.
Why use PgBouncer with PostgreSQL?
Each PostgreSQL connection is a separate process with real memory cost, so thousands of client connections hurt the server. PgBouncer keeps a small pool of server connections and shares them among many clients.
Where Admin fits in the PostgreSQL roadmap
Admin belongs to the Administration stage (advanced level). Keep it healthy.
Other units in this stage
Back to the full PostgreSQL roadmap