This release primarily fixes an issue with postgresql_conf
values of ipaddresses being considered floats and not getting quoted.
default_connect_settings
parameter to postgresql::server
This release contains some bugfixes and documentation updates.
$service_provider
parameter.A release with a considerable amount of new features, including remote db support and several platform support updates. Various bugfixes including several to address warnings and a sizable README update.
###Summary
Small release for support of newer PE versions. This increments the version of PE in the metadata.json file.
This release adds a proxy feature for yum, Postgis improvements, and decoupling pg_hba_rule from postgresql::server.
This release adds sequence grants, some postgresql 9.4 fixes, and onlyif
to
the psql resource.
onlyif
parameter to postgresql_psql
postgresql::server::grant::onlyif_exists
attributepostgresql::server::table_grant::onlyif_exists
attributepostgresql::server::grant
pg_hba_conf_defaults => false
to not disable ipv4/ipv6 aclspostgresql::server::pg_hba_rule
This release fixes a bug introduced in 4.4.0.
withenv
execution under Puppet 2.7. (MODULES-2185)This release fixes RHEL 7 & Fedora with manage_package_repo switched on.
This release has several new features, bugfixes, and test improvements.
postgresql::client
.postgresql::server::schema
titles unique. (MODULES-2049)postgresql_psql
parameter ordering to work on OpenBSD with Future ParserThis release fixes compatibility with Puppet 4 and removes opportunities for local users to view the postgresql password. It also adds a new custom resource to aid in managing replication.
postgresql::server::logdir
parameter to manage the logdirenvironment
parameter to postgresql_psql
postgresql_replication_slot
custom resourcepostgresql::validate_db_connection
for more than one host+port+database combopostgresql::server::extension
to work with custom user/group/portpostgresql::server::initdb
to work with custom user/group/portpostgresql::server::grant::object_name
valuepuppet::server::grant
##2015-03-10 - Supported Release 4.2.0 ###Summary
This release has several new features including support for server extensions, improved grant support, and a number of bugfixes.
####Features
service_reload
parameter to postgresql::server
comment
parameter to postgresql::server::database
(MODULES-1153)postgresql::server::extension
defined typepostgresql::server::grant
to support 'GRANT SCHEMA' and 'ALL TABLES IN SCHEMA'####Bugfixes
service_status
default for FreeBSD to allow PostgreSQL to start the first runpostgresql::server::grant
commentspg_config
should not be overwritten (MODULES-1485)##2014-11-04 - Supported Release 4.1.0 ###Summary
This release adds the ability to change the PGDATA directory, and also includes documentation and test updates, future parser support, and a few other new features.
####Features
/etc/sysconfig/pgsql/postgresql-${version}
to /etc/sysconfig/pgsql/postgresql
to support init scripts from the postgresql.org repo##2014-09-03 - Supported Release 4.0.0 ###Summary
This release removes the uninstall ability from the module, removes the firewall management, overhauls all of the acceptance testing, as well as adds better support for SuSE and Fedora.
###Backwards Incompatible changes.
####Uninstallation removal
We rely heavily on the ability to uninstall and reinstall postgres throughout our testing code, testing features like "can I move from the distribution packages to the upstream packages through the module" and over time we've learnt that the uninstall code simply doesn't work a lot of the time. It leaves traces of postgres behind or fails to remove certain packages on Ubuntu, and generally causes bits to be left on your system that you didn't expect.
When we then reinstall things fail because it's not a true clean slate, and this causes us enormous problems during test. We've spent weeks and months working on these tests and they simply don't hold up well across the full range of PE platforms.
Due to all these problems we've decided to take a stance on uninstalling in general. We feel that in 2014 it's completely reasonable and normal to have a good provisioning pipeline combined with your configuration management and the "correct" way to uninstall a fully installed service like postgresql is to simply reprovision the server without it in the first place. As a general rule this is how I personally like to work and I think is a good practice.
####I'm not OK with this!
We understand that there are environments and situations in which it's not easy to do that. What if you accidently deployed Postgres on 100,000 nodes? In the future we're going to take a look at building some example 'profiles' to be found under examples/ within this module that can uninstall postgres on popular platforms. These can be modified and used in your specific case to uninstall postgresql. They will be much more brute force and reliant on deleting entire directories and require you to do more work up front in specifying where things are installed but we think it'll prove to be a much cleaner mechanism for this kind of thing rather than trying to weave it into the main module logic itself.
####Features
####Bugfixes
##2014-08-27 - Supported Release 3.4.3 ###Summary
This release fixes Ubuntu 10.04 with Facter 2.2.
####Features ####Bugfixes
##2014-07-31 - Supported Release 3.4.2 ###Summary
This release fixes recent Fedora versions.
####Features ####Bugfixes
##2014-07-15 - Supported Release 3.4.1 ###Summary
This release merely updates metadata.json so the module can be uninstalled and upgraded via the puppet module command.
##2014-04-14 - Supported Release 3.4.0 ###Summary
This feature rolls up several important features, the biggest being PostGIS
handling and allowing port
to be set on postgresql::server in order to
change the port that Postgres listens on. We've added support for RHEL7
and Ubuntu 14.04, as well as allowing you to manage the service via
service_ensure
finally.
####Features
perl_package_name
for installing bindings.service_ensure
for allowing control of services.postgis_version
and postgis class for installing postgis.port
for selecting the port Postgres runs on.default_db
to postgresql::server::database.inherit
to postgresql::server::role.####Bugfixes
##2014-03-04 - Supported Release 3.3.3 ###Summary
This is a supported release. This release removes a testing symlink that can cause trouble on systems where /var is on a seperate filesystem from the modulepath.
####Features ####Bugfixes ####Known Bugs
##2014-03-04 - Supported Release 3.3.2 ###Summary This is a supported release. It fixes a problem with updating passwords on postgresql.org distributed versions of PostgreSQL.
####Bugfixes
####Known Bugs
##2014-02-12 - Version 3.3.1 ####Bugfix:
##2014-01-28 - Version 3.3.0
###Summary
This release rolls up a bunch of bugfixes our users have found and fixed for us over the last few months. This improves things for 9.1 users, and makes this module usable on FreeBSD.
This release is dedicated to 'bma', who's suffering with Puppet 3.4.1 issues thanks to Puppet::Util::SUIDManager.run_and_capture.
####Features
xlogdir
parameter.####Bugfixes
##2013-11-05 - Version 3.2.0
###Summary
Add's support for Ubuntu 13.10 (and 14.04) as well as x, y, z.
####Features
####Bugs
##2013-10-25 - Version 3.1.0
###Summary
This is a minor feature and bug fix release.
Firstly, the postgresql_psql type now includes a new parameter search_path
which is equivalent to using set search_path
which allows you to change the default schema search path.
The default version of Fedora 17 has now been added, so that Fedora 17 users can enjoy the module.
And finally we've extended the capabilities of the defined type postgresql::validate_db_connection so that now it can handle retrying and sleeping between retries. This feature has been monopolized to fix a bug we were seeing with startup race conditions, but it can also be used by remote systems to 'wait' for PostgreSQL to start before their Puppet run continues.
####Features
####Bugs
##2013-10-14 - Version 3.0.0
Final release of 3.0, enjoy!
##2013-10-14 - Version 3.0.0-rc3
###Summary
Add a parameter to unmanage pg_hba.conf to fix a regression from 2.5, as well as allowing owner to be passed into x.
####Features
manage_pg_hba_conf
parameter added to control pg_hba.conf management.owner
parameter added to server::db.##2013-10-09 - Version 3.0.0-rc2
###Summary
A few bugfixes have been found since -rc1.
####Fixes
##2013-10-01 - Version 3.0.0-rc1
###Summary
Version 3 was a major rewrite to fix some internal dependency issues, and to make the new Public API more clear. As a consequence a lot of things have changed for version 3 and older revisions that we will try to outline here.
(NOTE: The format of this CHANGELOG differs to normal in an attempt to explain the scope of changes)
postgresql::server::
namespace:To restructure server specific elements under the postgresql::server::
namespaces the following objects were renamed as such:
postgresql::database
-> postgresql::server::database
postgresql::database_grant
-> postgresql::server::database_grant
postgresql::db
-> postgresql::server::db
postgresql::grant
-> postgresql::server::grant
postgresql::pg_hba_rule
-> postgresql::server::pg_hba_rule
postgresql::plperl
-> postgresql::server::plperl
postgresql::contrib
-> postgresql::server::contrib
postgresql::role
-> postgresql::server::role
postgresql::table_grant
-> postgresql::server::table_grant
postgresql::tablespace
-> postgresql::server::tablespace
postgresql::server::config_entry
resource for managing configuration:Previously we used the file_line
resource to modify postgresql.conf
. This
new revision now adds a new resource named postgresql::server::config_entry
for managing this file. For example:
postgresql::server::config_entry { 'check_function_bodies':
value => 'off',
}
If you were using file_line
for this purpose, you should change to this new
methodology.
postgresql_puppet_extras.conf
has been removed:Now that we have a methodology for managing postgresql.conf
, and due to
concerns over the file management methodology using an exec { 'touch ...': }
as a way to create an empty file the existing postgresql_puppet_extras.conf
file is no longer managed by this module.
If you wish to recreate this methodology yourself, use this pattern:
class { 'postgresql::server': }
$extras = "/tmp/include.conf"
file { $extras:
content => 'max_connections = 123',
notify => Class['postgresql::server::service'],
}->
postgresql::server::config_entry { 'include':
value => $extras,
}
charset
changed to encoding
:Since PostgreSQL uses the terminology encoding
not charset
the parameter
has been made consisent across all classes and resources.
postgresql
base class is no longer how you set globals:The old global override pattern was less then optimal so it has been fixed,
however we decided to demark this properly by specifying these overrides in
the class postgresql::global
. Consult the documentation for this class now
to see what options are available.
Also, some parameter elements have been moved between this and the
postgresql::server
class where it made sense.
config_hash
parameter collapsed for the postgresql::server
class:Because the config_hash
was really passing data through to what was in
effect an internal class (postgresql::config
). And since we don't want this
kind of internal exposure the parameters were collapsed up into the
postgresql::server
class directly.
If you were using these before, these have changed names. You should only use what is documented in this README.md, and if you don't have what you need you should raise a patch to add that feature to a public API. All internal classes now have a comment at the top indicating them as private to make sure the message is clear that they are not supported as Public API.
pg_hba_conf_defaults
parameter included to turn off default pg_hba rules:The defaults should be good enough for most cases (if not raise a bug) but if you simply need an escape hatch, this setting will turn off the defaults. If you want to do this, it may affect the rest of the module so make sure you replace the rules with something that continues operation.
postgresql::database_user
has now been removed:Use postgresql::server::role
instead.
postgresql::psql
resource has now been removed:Use postgresql_psql
instead. In the future we may recreate this as a wrapper
to add extra capability, but it will not match the old behaviour.
postgresql_default_version
fact has now been removed:It didn't make sense to have this logic in a fact any more, the logic has been
moved into postgresql::params
.
ripienaar/concat
is no longer used, instead we use puppetlabs/concat
:The older concat module is now deprecated and moved into the
puppetlabs/concat
namespace. Functionality is more or less identical, but
you may need to intervene during the installing of this package - as both use
the same concat
namespace.
##2013-09-09 Release 2.5.0
###Summary
The focus of this release is primarily to capture the fixes done to the types and providers to make sure refreshonly works properly and to set the stage for the large scale refactoring work of 3.0.0.
####Features
####Bugfixes
##2013-08-01 Release 2.4.1
###Summary
This minor bugfix release solves an idempotency issue when using plain text passwords for the password_hash parameter for the postgresql::role defined type. Without this, users would continually see resource changes everytime your run Puppet.
####Bugfixes
##2013-07-19 Release 2.4.0
###Summary
This updates adds the ability to change permissions on tables, create template
databases from normal databases, manage PL-Perl's postgres package, and
disable the management of pg_hba.conf
.
####Features
postgresql::table_grant
defined resourcepostgresql::plperl
classmanage_pg_hba_conf
parameter to the postgresql::config
classistemplate
parameter to the postgresql::database
define####Bugfixes
postgresql::role
class to be able to update roles when modified
instead of only on creation.postgresql::database_grant
##2.3.0
This feature release includes the following changes:
owner
to the database
type. This can be used to
grant ownership of a new database to a specific user. (Bruno Harbulot)##2.2.1
This release fixes a bug whereby one of our shell commands (psql) were not ran from a globally accessible directory. This was causing permission denied errors when the command attempted to change user without changing directory.
Users of previous versions might have seen this error:
Error: Error executing SQL; psql returned 256: 'could not change directory to "/root"
This patch should correct that.
##2.2.0
This feature release introduces a number of new features and bug fixes.
First of all it includes a new class named postgresql::python
which provides you with a convenient way of install the python Postgresql client libraries.
class { 'postgresql::python':
}
You are now able to use postgresql::database_user
without having to specify a password_hash, useful for different authentication mechanisms that do not need passwords (ie. cert, local etc.).
We've also provided a lot more advanced custom parameters now for greater control of your Postgresql installation. Consult the class documentation for PuppetDB in the README.
This release in particular has largely been contributed by the community members below, a big thanks to one and all.
##2.1.1
This release provides a bug fix for RHEL 5 and Centos 5 systems, or specifically systems using PostgreSQL 8.1 or older. On those systems one would have received the error:
Error: Could not start Service[postgresqld]: Execution of ‘/sbin/service postgresql start’ returned 1:
And the postgresql log entry:
FATAL: unrecognized configuration parameter "include"
This bug is due to a new feature we had added in 2.1.0, whereby the include
directive in postgresql.conf
was not compatible. As a work-around we have added checks in our code to make sure systems running PostgreSQL 8.1 or older do not have this directive added.
2013-01-21 - Ken Barber ken@bob.sh
include
directive and included file on PostgreSQL >= 8.2##2.1.0
This release is primarily a feature release, introducing some new helpful constructs to the module.
For starters, we've added the line include 'postgresql_conf_extras.conf'
by default so extra parameters not managed by the module can be added by other tooling or by Puppet itself. This provides a useful escape-hatch for managing settings that are not currently managed by the module today.
We've added a new defined resource for managing your tablespace, so you can now create new tablespaces using the syntax:
postgresql::tablespace { 'dbspace':
location => '/srv/dbspace',
}
We've added a locale parameter to the postgresql
class, to provide a default. Also the parameter has been added to the postgresql::database
and postgresql::db
defined resources for changing the locale per database:
postgresql::db { 'mydatabase':
user => 'myuser',
password => 'mypassword',
encoding => 'UTF8',
locale => 'en_NG',
}
There is a new class for installing the necessary packages to provide the PostgreSQL JDBC client jars:
class { 'postgresql::java': }
And we have a brand new defined resource for managing fine-grained rule sets within your pg_hba.conf access lists:
postgresql::pg_hba { 'Open up postgresql for access from 200.1.2.0/24':
type => 'host',
database => 'app',
user => 'app',
address => '200.1.2.0/24',
auth_method => 'md5',
}
Finally, we've also added Travis-CI support and unit tests to help us iterate faster with tests to reduce regression. The current URL for these tests is here: https://travis-ci.org/puppetlabs/puppet-postgresql. Instructions on how to run the unit tests available are provided in the README for the module.
A big thanks to all those listed below who made this feature release possible :-).
2013-01-18 - Simão Fontes simaofontes@gmail.com & Flaper Fesp flaper87@gmail.com
2013-01-18 - Lauren Rother lauren.rother@puppetlabs.com
2013-01-09 - Adrien Thebo git@somethingsinistral.net
2013-01-28 - Karel Brezina karel.brezina@gmail.com
2013-01-16 - Chris Price chris@puppetlabs.com & Karel Brezina karel.brezina@gmail.com
2013-01-31 - jv jeff@jeffvier.com
2013-02-03 - Ken Barber ken@bob.sh
2013-02-02 - Ken Barber ken@bob.sh
2013-01-21 - Michael Arnold github@razorsedge.org
2013-02-06 - fhrbek filip.hbrek@gmail.com
2013-02-10 - Ken Barber ken@bob.sh
2013-02-11 - Ken Barber ken@bob.sh
2013-02-15 - Erik Dalén dalen@spotify.com
2013-02-15 - Erik Dalén dalen@spotify.com
##2.0.1
Minor bugfix release.
2013-01-16 - Chris Price chris@puppetlabs.com
43ded42
)2013-01-15 - Jordi Boggiano j.boggiano@seld.be
##2.0.0
Many thanks to the following people who contributed patches to this release:
Notable features:
Add support for versions of postgres other than the system default version
(which varies depending on OS distro). This includes optional support for
automatically managing the package repo for the "official" postgres yum/apt
repos. (Major thanks to Etienne Pelletier epelletier@maestrodev.com and
Ken Barber ken@bob.sh for their tireless efforts and patience on this
feature set!) For example usage see tests/official-postgresql-repos.pp
.
Add some support for Debian Wheezy and Ubuntu Quantal
Add new postgres_psql
type with a Ruby provider, to replace the old
exec-based psql
type. This gives us much more flexibility around
executing SQL statements and controlling their logging / reports output.
Major refactor of the "spec" tests--which are actually more like acceptance tests. We now support testing against multiple OS distros via vagrant, and the framework is in place to allow us to very easily add more distros. Currently testing against Cent6 and Ubuntu 10.04.
Fixed a bug that was preventing multiple databases from being owned by the
same user
(9adcd182f8
- Etienne Pelletier epelletier@maestrodev.com)
Add support for ACLs for finer-grained control of user/interface access
(b8389d19ad
- dharwood harwoodd@cat.pdx.edu)
Many other bug fixes and improvements!
##1.0.0
2012-09-17 - Version 0.3.0 released
2012-09-14 - Chris Price chris@puppetlabs.com
ce4a049
)2012-08-25 - Jari Bakken jari.bakken@gmail.com
e6af5e5
)2012-08-16 - Version 0.2.0 released