anchor.diff:  psql -h 127.0.0.1 -p 12001 -U postgres postgres -c 'table pitrtest'
   ....
   
  -This sql command should show that the pitrtest table does not exist
  -at this recovery time.
  +This SQL command should show that the pitrtest table does not exist
  +at this recovery time. The output should be similar to:
   
   PostgreSQL allows you to pause the recovery process if the target name
   or time is specified.  This pause would allow a DBA a chance to review
  
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: 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 documentation for
  full details.
  
  ==== Kubernetes
  