You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
*[Configuring the server](#configuring-the-server)
10
12
4.[Usage - How to use the module for various tasks](#usage)
11
13
5.[Upgrading - Guide for upgrading from older revisions of this module](#upgrading)
12
14
6.[Reference - The classes, defines,functions and facts available in this module](#reference)
@@ -47,6 +49,15 @@ The postgresql module offers many security configuration settings. Before gettin
47
49
48
50
Your answers to these questions will determine which of the module's parameters you'll want to specify values for.
49
51
52
+
###PE 3.2 supported module
53
+
54
+
PE 3.2 introduces Puppet Labs supported modules. The version of the postgresql module that ships within PE 3.2 is supported via normal [Puppet Enterprise support](http://puppetlabs.com/services/customer-support) channels. If you would like to access the [supported module](http://forge.puppetlabs.com/supported) version, you will need to uninstall the shipped module and install the supported version from the Puppet Forge. You can do this by first running
55
+
56
+
# puppet module uninstall puppetlabs-postgresql
57
+
and then running
58
+
59
+
# puppet module install puppetlabs/postgresql
60
+
50
61
###Configuring the server
51
62
52
63
The main configuration you'll need to do will be around the `postgresql::server` class. The default parameters are reasonable, but fairly restrictive regarding permissions for who can connect and from where. To manage a PostgreSQL server with sane defaults:
0 commit comments