Fix wrong config option
Update apt.postgresql.org key url 

Accordingly to http://wiki.postgresql.org/wiki/Apt the correc key_source url is https://www.postgresql.org/media/keys/ACCC4CF8.asc

Today the old file was removed, so it's urgent to update this file and made a new release
tag postgresql-jdbc package to fix package repo dependency
remove trailing commas
Support Debian Jessie
Merge pull request #409 from mnencia/patch-1

Update apt.postgresql.org key url
Set falback postgis_version to undef so that catalog still compiles if default postgresql version is unknown
Change selector statements to have default listed last

As per the official docs "the default case must be at the end of the list."
http://docs.puppetlabs.com/puppet/latest/reference/lang_conditional.html#selectors

This commit fixes breakage in Puppet 3.6.0 where it enforces the behavior
described above when Future parser is enabled.

See https://tickets.puppetlabs.com/browse/PUP-2642
Merge pull request #408 from fredj/readme-typo

Fix wrong config option in README
Merge pull request #421 from blkperl/puppet36_future_parser

Change selector statements to have default listed last
Ensure db user exists before validating db connection

The validate_db_connection class takes a user to connect as, but if we're
using the progresql::server::db defined type then the user might not be
created yet, and might not have any permissions granted yet.  This patch
users a collector to ensure that the that the user and grants are active
before validating.
Remove eq('') tests thanks to the new deprecation warnings.
Merge pull request #424 from apenney/remove-eq-tests

Remove eq('') tests thanks to the new deprecation warnings.
(MODULES-775) Fix refresh/unless parameter interactions

Interactions between resource refreshes and the 'unless' parameter have been
fixed to follow the behaviour of the 'exec' type.

The 'unless' parameter is now always taken into account, whether in ordinary
operation, during a refresh, or when refreshonly is set to true.  The resource
will not run the SQL command when the 'unless' clause matches a row.

Previously a refresh on a resource would ignore the 'unless' parameter if set
which could cause a failure re-running a command, such as attempting to create
a role that already exists.

The following examples have been fixed:

  * should not run SQL when refreshed and the unless query returns rows
  * with refreshonly should not run SQL when the unless query returns no rows
  * with refreshonly should not run SQL when refreshed and the unless query
    returns rows

This is done by moving the logic for refreshonly and whether to run the SQL
command from the provider into the type, and consolidating it in the
should_run_sql method which is called during 'command' property retrieval
(instead of sync) and during refresh.
Merge pull request #426 from domcleal/modules-775-refresh

(MODULES-775) Fix refresh/unless parameter interactions
Fix Ubuntu 14.04 tests for now.

This doesn't fix the root cause of the issue, such as the fact that
dpkg can't do wildcard removals, and the uninstall fails when you're
passing in a version number like this, but THIS test doesn't care, it
just wants to make sure the deprecation warning appears in the first
place.

This does however make the tests pass on 14.04.
Merge pull request #427 from apenney/fix-1404-tests

Fix Ubuntu 14.04 tests for now.
Merge pull request #419 from mcanevet/fix/unknown_postgis_version

Set fallback postgis_version to undef so that catalog still compiles if d...
Merge pull request #414 from lucas42/patch-1

Support Debian Jessie
Merge pull request #422 from dvorak/create_user_role_before_validate

Ensure db user exists before validating db connection