anchor.diff:  and the test table should be present.  When you recover the entire
   WAL history, resuming the recovery is not necessary to enable writes.
   
  -Other options exist for performing a PITR, see the pitr.adoc for
  +Other options exist for performing a PITR. See the pitr.adoc documentation for
   full details.
   
   ==== Kubernetes
  
positive.code: ./run-restore-pitr.sh
  ....
  
  
  After this restore, you should be able to see the test table:
  ....
  psql -h 127.0.0.1 -p 12001 -U postgres postgres -c 'table pitrtest'
  psql -h 127.0.0.1 -p 12001 -U postgres postgres -c 'select pg_xlog_replay_resume()'
  ....
  
  
  Lastly, lets recovery using all of the WAL files, this will get the
  restored database as current as possible, edit the script
  to remove the RECOVERY_TARGET_NAME environment setting completely:
  ....
  ./run-restore-pitr.sh
  
negative.code: another directory inside of this path with a name similar to
  *2016-09-21-21-03-29*.  Copy and paste that value into the
  run-restore-pitr.sh script in the *BACKUP* environment variable.
  
  In order to restore the database before we created test table in the
  last command, you'll need uncomment to the RECOVERY_TARGET_NAME label
  *-e RECOVERY_TARGET_NAME=beforechanges* to define the restore target name.
  After that, run the script.
  ....
  vi ./run-restore-pitr.sh
  ./run-restore-pitr.sh
  ....
  
  