anchor.diff:  reference when creating our restored database.  Points before
   and after the test table were made.
   
  -Next, lets edit the restore script to use the base backup files
  +Next, let's edit the restore script to use the base backup files
   created in the step above.  You can view the backup path name
   under the /tmp/backups/master-pitr-backups/ directory. You will see
   another directory inside of this path with a name similar to
  
positive.code: need to define your own custom postgresql.conf file and mount
  it to override the default postgresql.conf file.
  
  To run this example, run the following to create a
  database container:
  
  ....
  cd $CCPROOT/examples/docker/pgaudit
  
negative.code:  *  PG_PASSWORD
   *  PG_DATABASE
  
  === Password Management
  
  When you backup a database, the original user IDs and password credentials
  are copied over from the original database and saved. Because of this, you
  cannot use generated passwords as the new passwords will not be the same as the
  passwords stored in the backup.
  
  You have various options to deal with managing your
  passwords:
  