pg tablespace
Overview
This puppet type allows you to create drop and manage postgres tablespaces. Here is an example on how you could use it:
pg_tablespace {'my_ts@instance:
location => '/u01/pg_data',
owner => 'my_role',
}
The pg_tablespace
type recognises all of the options you also have when using SQL to create a user or a role.
Attributes
Attribute Name | Short Description |
---|---|
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. |
instance | Postgres instance to connect to. |
location | TThe location where the tablespace will store it’s data files. |
name | The full name of the tablespace including the name of the database. |
oid | The ID of role |
owner | The role name of the user who will own the new tablespace, or DEFAULT to use the default (namely, the user executing the command). |
provider | resource. |
tablespace_name | The tablespace name |
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_tablespace
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_tablespace
ensure
The basic property that the resource should be in.
Valid values are present
, absent
.
Back to overview of pg_tablespace
instance
Postgres instance to connect to.
All types have a name like resource@instance
.
Back to overview of pg_tablespace
location
TThe location where the tablespace will store it’s data files.
Back to overview of pg_tablespace
name
The full name of the tablespace including the name of the database.
Back to overview of pg_tablespace
oid
The ID of role
Back to overview of pg_tablespace
owner
The role name of the user who will own the new tablespace, or DEFAULT to use the default (namely, the user executing the command). To create a database owned by another role, you must be a direct or indirect member of that role, or be a superuser.
Back to overview of pg_tablespace
provider
The specific backend to use for this pg_tablespace
resource. You will seldom need to specify this — Puppet will usually discover the appropriate provider for your platform.Available providers are:
- simple
- Manage Postgres tablespaces via regular SQL
Back to overview of pg_tablespace
tablespace_name
The tablespace name