graphql-engine/.circleci/pgbouncer/pgbouncer.ini

[databases]
hs_hge_test = host=localhost port=5432 dbname=hs_hge_test user=gql_test

[pgbouncer]
listen_port = 6543
listen_addr = 127.0.0.1
logfile = pgbouncer/pgbouncer.log
pidfile = pgbouncer/pgbouncer.pid
auth_type = md5
auth_file = pgbouncer/users.txt
admin_users = postgres
sync metadata cache across multiple instances connected to same db (closes #1182) (#1574) 1. Haskel library `pg-client-hs` has been updated to expose a function that helps listen to `postgres` notifications over a `channel` in this [PR](https://github.com/hasura/pg-client-hs/pull/5) 2. The server records an event in a table `hdb_catalog.hdb_cache_update_event` whenever any `/v1/query` (that changes metadata) is requested. A trigger notifies a `cache update` event via `hasura_cache_update` channel 3. The server runs two concurrent threads namely `listener` and `processor`. The `listener` thread listens to events on `hasura_cache_update` channel and pushed into a `Queue`. The `processor` thread fetches events from that `Queue` and processes it. Thus server rebuilds schema cache from database and updates. 2019-03-12 08:46:27 +03:00			`[databases]`
			`hs_hge_test = host=localhost port=5432 dbname=hs_hge_test user=gql_test`

			`[pgbouncer]`
			`listen_port = 6543`
			`listen_addr = 127.0.0.1`
			`logfile = pgbouncer/pgbouncer.log`
			`pidfile = pgbouncer/pgbouncer.pid`
			`auth_type = md5`
			`auth_file = pgbouncer/users.txt`
			`admin_users = postgres`