anchor.diff:  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
  +to a replica database.
  +
  +To test this failover, you first create a running master/replica
   cluster as follows:
   
   ....
  
positive.code: psql -h 127.0.0.1 -p 12000 -U postgres postgres -c 'table pg_stat_replication'
  ....
  
  You should see 2 rows, 1 for the async slave and 1 for the sync slave.  The
  sync_state column shows values of async or sync.
  
  You can test replication to the slaves by entering some data on
  the master like this, and then querying the slaves for that data:
  ....
  psql -h 127.0.0.1 -p 12000 -U postgres postgres -c 'create table foo (id int)'
  psql -h 127.0.0.1 -p 12000 -U postgres postgres -c 'insert into foo values (1)'
  
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:
  
  