Once we have compiled and installed PgBouncer, we can easily fire it up. To do so, we have set up two databases on a local instance (p0 and p1). The idea behind the setup performed in this example is to use PgBouncer as a proxy.
To make PgBouncer work, we can write a simple config file, and this file can be fed to PgBouncer:
[databases] p0 = host=localhost dbname=p0 p1 = host=localhost dbname=p1 [pgbouncer] logfile = /var/log/pgbouncer.log pidfile = /var/log/pgbouncer.pid listen_addr = 127.0.0.1 listen_port = 6432 auth_type = trust auth_file = /etc/pgbouncer/userlist.txt pool_mode = session server_reset_query = DISCARD ALL max_client_conn = 100 default_pool_size = 20
Using the same database name is not required here. You can map any database name to any connect strings. We have just found it useful to use identical names.
Once we have written this config file, we can safely start PgBouncer and see what...