Added info about the advanced configuration file

Author: kbrezina

README.md

@@ -12,7 +12,7 @@ postgresql
 8. [Disclaimer - Licensing information](#disclaimer)
 9. [Transfer Notice - Notice of authorship change](#transfer-notice)
 10. [Contributors - List of module contributors](#contributors)
-8. [Release Notes - Notes on the most recent updates to the module](#release-notes)
+11. [Release Notes - Notes on the most recent updates to the module](#release-notes)
 
 
 Overview
@@ -72,6 +72,9 @@ Once you've completed your configuration of `postgresql::server`, you can test o
 
 If you get an error message from these commands, it means that your permissions are set in a way that restricts access from where you’re trying to connect. That might be a good thing or a bad thing, depending on your goals.
 
+Advanced configuration setting parameters can be placed into `postgresql_puppet_extras.conf` (located in the same folder as `postgresql.conf`). You can manage that file as a normal puppet file resource, or however you see fit; which gives you complete control over the settings. Any value you specify in that file will override any existing value set in the templated version.  
+For more details about server configuration parameters see http://www.postgresql.org/docs/9.2/static/runtime-config.html.
+
 ###Configuring the database
 
 There are many ways to set up a postgres database using the `postgresql::db` class. For instance, to set up a database for PuppetDB (this assumes you’ve already got the `postgresql::server` set up to your liking in your manifest, as discussed above):
@@ -199,6 +202,10 @@ This class is used to manage the basic postgresql client packages (which include
 
 This defined type can be used to create a database with no users and no permissions, which is a rare use case. 
 
+**postgresql::tablespace** 
+
+This defined type can be used to create a tablespace.
+
 **postgresql_psql**
 
 This defined type manages the command line tool for the postgresql module.

manifests/server.pp

@@ -8,6 +8,12 @@
 # [*package_name*] - name of package
 # [*service_name*] - name of service
 #
+# Configuration:
+#   Advanced configuration setting parameters can be placed into 'postgresql_puppet_extras.conf' (located in the same
+#   folder as 'postgresql.conf'). You can manage that file as a normal puppet file resource, or however you see fit;
+#   which gives you complete control over the settings. Any value you specify in that file will override any existing
+#   value set in the templated version.
+#
 # Actions:
 #
 # Requires:
@@ -61,5 +67,4 @@
     onlyif      => $service_status,
     refreshonly => true,
   }
-
 }

spec/README.md

@@ -27,3 +27,8 @@ instead do something like:
 
 For some options that might speed up the testing process a bit during development,
 please see `spec/support/postgres_test_config.rb`.
+
+By default the sahara gem restores VMs to a snapshot state after each test,
+to make sure that the individual tests aren't polluting the ones that are run later.
+If you want to disable this during development, you can set HardCoreTesting to false
+in `spec/support/postgres_test_config.rb`.