postgres job from shield/6.5.4
              Github source:
              688eeff5 or
              master branch
            
Properties¶
databases¶
  
  
    
databases¶A list of databases and associated properties to create. Each entry in the list must have a ‘name’ key defined. If the ‘citext’ key is set to a true value, the PostgreSQL citext extension will be installed. The optional ‘run_on_every_startup’ parameter can be set to a valid SQL query to run everytime the monit job starts. Example: databases: databases: - name: shielddb citext: true
log_level¶PostgreSQL log level, one of DEBUG{1..5}, LOG, NOTICE, WARNING, ERROR, FATAL or PANIC.
- Default
ERROR
log_line_prefix¶The postgres
printfstyle string that is output at the beginning of each log line
- Default
'%m: '
max_connections¶Maximum number of database connections
port¶Port to listen on
roles¶A list of database users (roles) to create. Each entry in the list must be a map containing at least the ‘name’ and ‘password’ keys. An optional ‘permissions’ key can be set as a list of rights to assign the user. Example: databases: roles: - name: shieldadmin password: its-a-secret
Templates¶
            Templates are rendered and placed onto corresponding
            instances during the deployment process. This job's templates
            will be placed into /var/vcap/jobs/postgres/ directory
            (learn more).
          
- bin/postgres_ctl(from- bin/postgres_ctl)
- bin/postgres_start.sh(from- bin/postgres_start.sh)
- config/pg_hba.conf(from- config/pg_hba.conf)
- config/postgresql.conf(from- config/postgresql.conf)
Packages¶
            Packages are compiled and placed onto corresponding
            instances during the deployment process. Packages will be
            placed into /var/vcap/packages/ directory.