anchor.diff:  ....
   
   At this point, the pgbouncer will notice that the master is not reachable
  -and touch the trigger file on the configured slave database to start
  +and touch the trigger file on the configured replica database to start
   the failover.  The pgbouncer container will then reconfigure
  -pgbouncer to relabel the slave database into the master database so clients
  +pgbouncer to relabel the replica database into the master database so clients
   to pgbouncer will be able to connect to the master as before the failover.
   
   To just log into the database from the pgbouncer connection pool
  
positive.code: The pgbouncer utility can be used to provide a connection pool
  to postgres databases.  The crunchy-pgbouncer container also
  contains logic that lets it perform a failover from a master
  to a slave database.
  
  To test this failover, you first create a running master/slave
  cluster as follows:
  
  ....
  
negative.code: 
  This example, $CCPROOT/examples/docker/sync, provides a
  streaming replication configuration that includes both
  synchronous and asynchronous replicas.
  
  To run this example, run the following:
  
  