Nordic PGDay will once again return to Copenhagen for

Hello,

Greetings from India PostgreSQL User Group! We are pleased to announce that

The PostgreSQL Global Development Group announces that the first release candidate of PostgreSQL

The pg_hint_plan development team is pleased to announce pg_hint_plan 1.7.0. This release of pg_

EDB is pleased to announce the release of Barman 3.11.1 and 3.11.0.

PG Failover Slots 1.1.0 Released

EDB is pleas

fish's dotNET is proud to announce version 36.3 of Database .NET, an innovative,

The PostgreSQL JDBC project is excited to announce the release of version 42.7.4 This is mostly a

The CloudNativePG Community is excited to announce the release of CloudN

The pgAdmin Development Team is pleased to announce pgAdmin 4 version 8.11. This release of pgAdm

What is Pgpool-II?

Pgpool-II is a tool to add useful features to PostgreSQL, including:

WAL-G team is happy to announce the release of WAL-G 3.0.3

WAL-G is a tool for archival da

Pigsty v3.0 (beta) introduces a public Y

The PostgreSQL Global Development Group has released an update to all supported versions of Postg

New browser-based tool is open source and designed especially for managing PostgreSQL databases

Oxford, United Kingdom - August 22, 2017

SQL Maestro Group announces the release of PostgreSQL Maestro 17.8, a powerful Windows GUI solution for PostgreSQL database server administration and database development.

The new version is immediately available for download.

Top 10 new features:

1. PostgreSQL 10 compatibility.
2. Support for Native Table Partitioning (PostgreSQL 10).
3. Support for Identity Columns (PostgreSQL 10).
4. Support for Restrictive RLS Policies (PostgreSQL 10).
5. Custom captions and colors for server nodes in Database Explorer.
6. New Statistics tab in the Edit Database Profile dialog.
7. Improved Data Grid.
8. New SQL Editor options.
9. Links to our Socials at the Quick Launch panel.
10. Some performance and usability improvements.

There are also some other useful things. Full press release is available at the SQL Maestro Group website.

The PostgreSQL Global Development Group announces today that the third beta release of PostgreSQL 10 is available for download. This release contains previews of all of the features which will be available in the final release of version 10, including fixes to many of the issues found in the second beta. Users are encouraged to begin testing their applications against 10 beta3.

Upgrading to Beta3

PostgreSQL 10 beta3 requires an upgrade from beta1, beta2, or earlier either using pg_dump / pg_restore or pg_upgrade.

Any bugfixes applied to 9.6 or earlier that also affected 10 are included in beta3. Our users and contributors also reported bugs against 10 beta 2, and many of them have been fixed in this release. We urge our community to re-test to ensure that these bugs are actually fixed, including:

• hash: Fix write-ahead logging bugs related to init forks
• Fix oddity in error handling of constraint violation in ExecConstraints for partitioned tables
• Use a real RT index when setting up partition tuple routing
• Fix serious performance problems in json(b) to_tsvector()
• Fix problems defining multi-column range partition bounds
• Fix partitioning crashes during error reporting
• Fix race conditions in replication slot operations
• Fix very minor memory leaks in psql's command.c
• PL/Perl portability fix: avoid including XSUB.h in plperl.c
• Fix inadequate stack depth checking in the wake of expression execution changes
• Allow creation of C/POSIX collations without depending on libc behavior
• Fix OBJECT_TYPE/OBJECT_DOMAIN confusion
• Remove duplicate setting of SSL_OP_SINGLE_DH_USE option
• Fix crash with logical replication on a function index
• Teach map_partition_varattnos to handle whole-row expressions
• Fix lock upgrade hazard in ATExecAttachPartition
• Apply ALTER ... SET NOT NULL recursively in ALTER ... ADD PRIMARY KEY
• hash: Increase the number of possible overflow bitmaps by 8x
• Only kill sync workers at commit time in subscription DDL
• Fix bug in deciding whether to scan newly-attached partition
• Make pg_stop_backup's wait_for_archive flag work on standbys
• Fix handling of dropped columns in logical replication
• Fix local/remote attribute mix-up in logical replication

Note that some known issues remain unfixed. Before reporting a bug in the beta, please check the Open Items page.

Beta Schedule

This is the third beta release of version 10. The PostgreSQL Project will release additional betas as required for testing, followed by one or more release candidates, until the final release in late 2017. For further information please see the Beta Testing page. Links

• Downloads Page

• Beta Testing Information

• 10 Beta Release Notes

• What's New in 10

• 10 Open Items

The PostgreSQL Global Development Group has released an update to all supported versions of our database system, including 9.6.4, 9.5.8, 9.4.13, 9.3.18, and 9.2.22. This release fixes three security issues. It also patches over 50 other bugs reported over the last three months. Users who are affected by the below security issues should update as soon as possible. Users affected by CVE-2017-7547 will need to perform additional steps after upgrading to resolve the issue. Other users should plan to update at the next convenient downtime.

Security Issues

Three security vulnerabilities have been closed by this release:

• CVE-2017-7546: Empty password accepted in some authentication methods
• CVE-2017-7547: The "pg_user_mappings" catalog view discloses passwords to users lacking server privileges
• CVE-2017-7548: lo_put() function ignores ACLs

CVE-2017-7546: Empty password accepted in some authentication methods

libpq, and by extension any connection driver that utilizes libpq, ignores empty passwords and does not transmit them to the server. When using libpq or a libpq-based connection driver to perform password-based authentication methods, it would appear that setting an empty password would be the equivalent of disabling password login. However, using a non-libpq based connection driver could allow a client with an empty password to log in.

To fix this issue, this update disables empty passwords from being submitted in any of the password-based authentication methods. The server will reject any empty passwords from being set on accounts.

CVE-2017-7547: The "pg_user_mappings" catalog view discloses passwords to users lacking server privileges

This fix pertains to the usage of the foreign data wrapper functionality, particularly for the user mapping feature.

Before this fix, a user had access to see the options in pg_user_mappings even if the user did not have the USAGE permission on the associated foreign server. This meant that a user could see details such as a password that might have been set by the server administrator rather than the user.

This fix will only fix the behavior in newly created clusters utilizing initdb. To fix this issue on existing systems, you will need to follow the below steps. For more details, please see the release notes.

1. In your postgresql.conf file, add the following:

   allow_system_table_mods = true
   

2. After adding that line, you will need to restart your PostgreSQL cluster.

3. In each database of the cluster, run the following commands as a superuser:

   SET search_path = pg_catalog;
   CREATE OR REPLACE VIEW pg_user_mappings AS
   SELECT
       U.oid       AS umid,
       S.oid       AS srvid,
       S.srvname   AS srvname,
       U.umuser    AS umuser,
       CASE WHEN U.umuser = 0 THEN
           'public'
       ELSE
           A.rolname
       END AS usename,
       CASE WHEN (U.umuser <> 0 AND A.rolname = current_user
                    AND (pg_has_role(S.srvowner, 'USAGE')
                         OR has_server_privilege(S.oid, 'USAGE')))
                   OR (U.umuser = 0 AND pg_has_role(S.srvowner, 'USAGE'))
                   OR (SELECT rolsuper FROM pg_authid WHERE rolname = current_user)
                   THEN U.umoptions
                ELSE NULL END AS umoptions
   FROM pg_user_mapping U
   LEFT JOIN pg_authid A ON (A.oid = U.umuser)
   JOIN pg_foreign_server S ON (U.umserver = S.oid);
   

4. You also need to run the command on your template0 and template1 databases, otherwise the vulnerability will exist in future databases that you create.

   First, you will need to allow template0 to accept connections. In PostgreSQL 9.5 you can run the following:

   ALTER DATABASE template0 WITH ALLOW_CONNECTIONS true;
   

   In PostgreSQL 9.4 and below, you will have to run this command:

   UPDATE pg_database SET datallowconn = true WHERE datname = 'template0';
   

   Then, in your template0 and template1 databases, run the commands as describe in Step 3

   When you are done, you will need to disallow connections from template0. In PostgreSQL 9.5, you can run the following:

   ALTER DATABASE template0 WITH ALLOW_CONNECTIONS false;
   

   In PostgreSQL 9.4 and below, you will have to run the following:

   UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
   

5. Remove the following line from your postgresql.conf file:

   allow_system_table_mods = false
   

6. Restart your PostgreSQL cluster

For more details, please see the release notes.

CVE-2017-7548: lo_put() function ignores ACLs

The lo_put() function should require the same permissions as lowrite(), but there was a missing permission check which would allow any user to change the data in a large object.

To fix this, the lo_put() function was changed to check the UPDATE privileges on the target object.

Bug Fixes and Improvements

This update also fixes a number of bugs reported in the last few months. Some of these issues affect only version 9.6, but many affect all supported versions:

• pg_upgrade: corrected the documentation about the process for upgrading standby servers to ensure the primary and standbys synchronized safely. Also includes a fix to ensure the last WAL record does not have "wal_level = minimum" which would prevent standbys from connecting upon restart
• Fix for issue with a concurrent locking race condition that could cause some of the updates to fail
• Several fixes for low probability data corruption scenarios
• Fix to prevent crash when sorting more than one billion tuples in-memory
• Fix on Windows to retry creating a process if shared memory addresses could not be allocated, typically caused from antivirus software interference
• Fix in libpq to ensure that failed connection attempts using GSS/SASL and SSPI authentication are reset properly
• Fixes for SSL connection handling and logging
• Fix to allow window functions to be used in sub-SELECT statements that are within the arguments of an aggregate function
• Allow parallelism in the query plan when COPY when copying from a query
• Several fixes to ALTER TABLE
• Fix to ensure that ALTER USER ... SET and ALTER ROLE ... SET accepts the same syntax variants
• Fixes for the statistics collector, ensuring statistics requests made just after a postmaster shutdown request will be written to disk
• Fix possible creation of an invalid WAL segment during standby promotion
• Several walsender / walreceiver fixes, particularly around signal handling and shutdowns / restarts
• Several logic decoding fixes, including removing leakage of small subtransactions to disk
• Allow a CHECK constraints to be initially NOT VALID when executing CREATE FOREIGN TABLE
• Fixes to postgres_fdw for applying changes promptly after ALTER SERVER / ALTER USER MAPPING commands and improving ability to escape from an unresponsive server
• Several fixes for pg_dump and pg_restore, including a fix for pg_dump output to stdout on Windows
• Fix pg_basebackup output to stdout on Windows, similar to the fix for pg_dump
• Fix pg_rewind to correctly handle files exceeding 2GB, though files of such size should rarely appear in a data directory
• Several fixes for building PostgreSQL with Microsoft Visual C (MSVC), primarily around sourcing libraries

EOL Warning for Version 9.2

PostgreSQL version 9.2 will be End-of-Life in September, 2017. The project expects to only release one more update for that version. We urge users to start planning an upgrade to a later version of PostgreSQL as soon as possible. See our Versioning Policy for more information.

Updating

All PostgreSQL update releases are cumulative. As with other minor releases, users are not required to dump and reload their database or use pg_upgrade in order to apply this update release; you may simply shut down PostgreSQL and update its binaries.

Links:

• Download

• Release Notes

• Security Page

• Versioning Policy

We are down to counting the days until PostgresOpen SV 2017 in downtown San Francisco, September 6th to 8th!

Check out our exciting schedule, which you can go to now here:

https://postgresql.us/events/schedule/pgopen2017/

There's only a week left to take advantage of our discounted hotel rate at the wonderful Parc 55 in downtown San Francisco! Get your hotel room booked now:

https://aws.passkey.com/e/49007744

Our trainings and sponsored workshops are filling up fast now, be sure to register for the conference and the sessions you're interested in:

https://2017.postgresopen.org/tickets/

Be sure to find and join your local PUG and PG-related meetups and get a discount code from them!

Special thanks to our sponsors! Be sure to check them out as we've just added on our third Diamond sponsor, and thanks to all of our Platinum, Gold, Silver, and Supporter sponsors, and we've now added Community Partners as well!

This year we are pleased to be able to recognize our three Diamond sponsors:

2ndQuadrant

CitusData

Microsoft

And our Platinum sponsor:

Heroku

Be sure to check out our site to see all of our Gold, Silver and Supporter sponsors, and our Community Partners here:

https://2017.postgresopen.org/sponsors/

Sponsorship opportunities are still available! Please visit https://2017.postgresopen.org/becomesponsor/ to review our prospectus.

PostgresOpen wouldn't be able to happen without the tireless efforts of the individuals at the United States PostgreSQL Association (PgUS), please consider joining!

https://postgresql.us

PgUS is the non-profit organization which backs PostgresOpen and other events, such as PGDay Austin happening in just a few weeks! Check it out here:

https://pgdayaustin2017.postgresql.us/

We look forward to seeing everyone in San Francisco in less than a month!

Any questions? Please contact: program2017@postgresopen.org.

I am very glad to announce the 2.1.0 version of E-Maj.

E-Maj is a PostgreSQL extension which enables fine-grained write logging and time travel on subsets of the database.

This new version supports from PostgreSQL 9.1 to PostgreSQL 10 versions. It represents a first step in giving more flexibility in tables groups management. It allows to change tables groups attributes without being obliged to stop/restart the logging mecanism (and lose the capability to 'rollback' to a previous point in time).

A new independant web GUI, named Emaj_web, is also available to help users in managing all their E-Maj operations.

Since a few months, the full documentation is also available on line.

The core extension is available at pgxn.org or github.org. It includes a general presentation and a detailed documentation.

The phpPgAdmin plugin and the Emaj_web application are also available at github.org.

Have fun with E-Maj !