anchor.diff:  | rhel7-9.6-1.4.1
   |===
   
  -=== Replica Database
  +=== Replica Database Template
   
   Template names is *crunchy-replica*
   
  
positive.code: | rhel7-9.6-1.4.1
  |===
  
  === pgadmin4 Web User Interface
  
  Template Name is *crunchy-pgadmin4*
  
  
negative.code: 172.30.149.135:5000/default
  ....
  
  === crunchy-postgres container
  
  The crunchy-postgres container executes the Postgres database. The *crunchy-master*,
  *crunchy-replica* and *crunchy-restore* templates utilize this container.
  
  *Packages*
  
  The container image is built using either the Crunchy Postgres release
  or the community version based upon a flag in the Makefile.
  
  The Crunchy postgres RPMs are available to Crunchy customers only.  The
  Crunchy release is meant for customers that require enterprise level
  support.
  
  The PGDG community RPMs can be used as well by simply commenting out
  the Crunchy yum repo within the Dockerfiles and uncommenting
  the PGDG yum repo.
  
  *setup.sql*
  
  The *setup.sql* script is used to define startup SQL commands that are
  executed when the database is first created.
  
  *Environment Variables*
  
   * PG_MODE - either *master*, *slave* or *set*, this value determines whether
     the database is set up as a master or slave instance, in the
     case of *set*, it means the container is started within a StatefulSet
     in a Kubernetes cluster.
   * PG_MASTER_USER - the value to use for the user ID created as
     master.  The *master* user has super user priviledges.
   * PG_MASTER_PASSWORD - the password for the PG_MASTER_USER database user
   * PG_USER - the value to use for the user ID created as a normal user.
     This user is created as part of the setup.sql script upon database
     creation and allows users to predefine an application user.
   * PG_PASSWORD - the password for the PG_USER database user that is created
   * PG_DATABASE - a database that is created upon database initialization
   * PG_ROOT_PASSWORD - the postgres user password set up upon database
     initialization
   * PG_LOCALE - if set, the locale you want to create the database with, if
     not set, the default locale is used
   * SYNC_SLAVE - if set, this value is used to specify the application_name
     of a slave that will be used for a synchronous replication
   * CHECKSUMS - if set, this value is used to enable the *--data-checksums*
     option when initdb is executed at initialization, if not set, the
     default is to *not* enable data checksums
   * XLOGDIR - if set, initdb will use the specified directory for WAL
   * ARCHIVE_MODE - if set to *on*, will enable continious WAL archiving
     by setting the value within the postgresql.conf file *archive_mode*
     setting, if not set, the default is *off*
   * ARCHIVE_TIMEOUT - if set to a number (in seconds) , will specify
     the postgresql.conf *archive_timeout* setting, if not set, the
     default value of *60* is used.
   * PGAUDIT_ANALYZE - if set, will cause the container to also start the
     pgaudit_analyze program in the background
   * PGDATA_PATH_OVERRIDE - if set, will cause the container to use a /pgdata path
     name of your choosing rather than the hostname of the container which
     is the default...this is useful for a master in a deployment.
  
  *Features*
  
  The following features are supported by the crunchy-postgres container:
  
   * use of openshift secrets
   * ability to restore from a database backup
   * use of custom pg_hba.conf and postgresql.conf files
   * ability to override postgresql.conf configuration parameters
   * ability to override the default setup.sql script
   * ability to set the database locale
   * ability to specify a synchronous slave application_name
   * ability to specify a recovery using PITR and WAL files, see
     pitr.asciidoc for a detailed design explaination of how PITR
     is implemented within the container suite
  
  *Locale Support*
  
  Adding locale support to the container is accomplished by
  running 'yum reinstall glibc_common' within the container, this
  increases the size of the container image and can be removed if you
  do not require specific locale support.
  
  You can specify the PG_LOCALE env var which is passed to the initdb
  command when the initial data files are created, for example:
  ....
  "name": "PG_LOCALE",
  "value": "fr_BE.UTF-8"
  ....
  
  By default, no locale is specified when the initdb command is executed.
  
  === Master Database Template
  
  Template Name is *crunchy-master*
  
  