Overview

This resource allows you create, manage and delete a Postgres cluster.

pg_cluster { '/database/db1':
  os_user => 'postgres',
}

A Postgres cluster is a location where Postgres stores the database content.

Experience the Power of Puppet for Postgres

If you want to play and experiment with Puppet and Postgres, please take a look at our playgrounds. At our playgrounds, we provide you with a pre-installed environment, where you experiment fast and easy.

For Postgres   here at our playground...

Attributes

Attribute Name Short Description
allow_group_access When set to true groups members have access to the created cluster.
db_user The Database superuser to use for creating the cluster
   
disable_corrective_change Disable the modification of a resource when Puppet decides it is a corrective change.
disable_corrective_ensure Disable the creation or removal of a resource when Puppet decides is a corrective change.
ensure The basic property that the resource should be in.
location The location of the software the cluster is running from.
name The name of the setting.
os_group The OS group to use for creating the cluster
   
os_user The OS user to use for creating the cluster
   
provider resource.
waldir The directory where the write-ahead log should be stored.

allow_group_access

When set to true groups members have access to the created cluster.

Back to overview of pg_cluster

db_user

The Database superuser to use for creating the cluster

Back to overview of pg_cluster

disable_corrective_change

Disable the modification of a resource when Puppet decides it is a corrective change.

(requires easy_type V2.11.0 or higher)

When using a Puppet Server, Puppet knows about adaptive and corrective changes. A corrective change is when Puppet notices that the resource has changed, but the catalog has not changed. This can occur for example, when a user, by accident or willingly, changed something on the system that Puppet is managing. The normal Puppet process then repairs this and puts the resource back in the state as defined in the catalog. This process is precisely what you want most of the time, but not always. This can sometimes also occur when a hardware or network error occurs. Then Puppet cannot correctly determine the current state of the system and thinks the resource is changed, while in fact, it is not. Letting Puppet recreate remove or change the resource in these cases, is NOT wat you want.

Using the disable_corrective_change parameter, you can disable corrective changes on the current resource.

Here is an example of this:

crucial_resource {'be_carefull':
  ...
  disable_corrective_change => true,
  ...
}

When a corrective ensure does happen on the resource Puppet will not modify the resource and signal an error:

    Error: Corrective change present requested by catalog, but disabled by parameter disable_corrective_change
    Error: /Stage[main]/Main/Crucial_resource[be_carefull]/parameter: change from '10' to '20' failed: Corrective change present requested by catalog, but disabled by parameter disable_corrective_change. (corrective)

Back to overview of pg_cluster

disable_corrective_ensure

Disable the creation or removal of a resource when Puppet decides is a corrective change.

(requires easy_type V2.11.0 or higher)

When using a Puppet Server, Puppet knows about adaptive and corrective changes. A corrective change is when Puppet notices that the resource has changed, but the catalog has not changed. This can occur for example, when a user, by accident or willingly, changed something on the system that Puppet is managing. The normal Puppet process then repairs this and puts the resource back in the state as defined in the catalog. This process is precisely what you want most of the time, but not always. This can sometimes also occur when a hardware or network error occurs. Then Puppet cannot correctly determine the current state of the system and thinks the resource is changed, while in fact, it is not. Letting Puppet recreate remove or change the resource in these cases, is NOT wat you want.

Using the disable_corrective_ensure parameter, you can disable corrective ensure present or ensure absent actions on the current resource.

Here is an example of this:

crucial_resource {'be_carefull':
  ensure                    => 'present',
  ...
  disable_corrective_ensure => true,
  ...
}

When a corrective ensure does happen on the resource Puppet will not create or remove the resource and signal an error:

    Error: Corrective ensure present requested by catalog, but disabled by parameter disable_corrective_ensure.
    Error: /Stage[main]/Main/Crucial_resource[be_carefull]/ensure: change from 'absent' to 'present' failed: Corrective ensure present requested by catalog, but disabled by parameter disable_corrective_ensure. (corrective)

Back to overview of pg_cluster

ensure

The basic property that the resource should be in.

Valid values are present, absent.

Back to overview of pg_cluster

location

The location of the software the cluster is running from.

Back to overview of pg_cluster

name

The name of the setting. This must be equal to the name of the database.

Back to overview of pg_cluster

os_group

The OS group to use for creating the cluster

Back to overview of pg_cluster

os_user

The OS user to use for creating the cluster

Back to overview of pg_cluster

provider

The specific backend to use for this pg_cluster resource. You will seldom need to specify this — Puppet will usually discover the appropriate provider for your platform.Available providers are:

simple
Register manage a postgres cluster

Back to overview of pg_cluster

waldir

The directory where the write-ahead log should be stored.

Back to overview of pg_cluster