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 !

PremiumSoft today released an upgraded version of Navicat for PostgreSQL version 12 in a brand new interface, with full support for PosgreSQL 9.6.

"In the latest version of Navicat, it comes with numerous improvements and features to address your PostgreSQL database development needs. With over 100 enhancements and a brand new interface — Navicat gives you new ways to build, manage, and maintain your PostgreSQL databases. ” said Ken Lin, Software Development Director at PremiumSoft CyberTech Ltd.

New key features in Navicat Version 12 includes:

• Brand new UI/UX design
• PostgreSQL Objects
  1. Support Foreign Server with User Mapping.
  2. Support Foreign Table.
  3. Support PostgreSQL Debugger.
  4. Enhanced Object Designers.
• A breakthrough engine that makes everything amazingly smooth.
• With the new On Startup feature and Touch Bar support, organizing your work and browsing your PostgreSQL database objects couldn't get any easier.
• A typo-free environment is easier to accomplish with advanced code completion.
• Brand new Structure Synchronization: compare objects before syncing your PostgreSQL databases.
• Brand new Data Synchronization: show particular status to distinguish the differences between records easily
• New Automation: optimize your PostgreSQL database activities with flexible database automation and scheduling.

Navicat Cloud Collaboration Capabilities With Navicat Cloud Collaboration, Navicat customers now have the ability to invite a colleague to work together on a project— to assign roles to members and have visibility into the activities in the Activity Log.

Free Trial and Availability

A Free 14-day Trial is also available for download, for more details please go to : https://www.navicat.com/en/download/navicat-for-postgresql

To learn more about Navicat for PostgreSQL, please visit: https://www.navicat.com/en/products/navicat-for-postgresql

About Navicat

Navicat develops the leading database management and development software. One of its top-rated products, Navicat Premium, allows you to access up to 6 databases all-in-one including MySQL, MariaDB, SQL Server, SQLite, Oracle, and PostgreSQL, eliminating workflow disruption to leverage users’ time and increasing productivity and efficiency.

About PremiumSoft

PremiumSoft CyberTech Ltd. is a multinational corporation headquartered in Hong Kong, the company was founded in 1999 and has developed numerous award-winning products over the years.

Oxford, United Kingdom - August 27, 2017

2ndQuadrant is proud to announce that the 2ndQuadrant PostgreSQL Conference 2017 (2Q PGConf, for short) will be hosted on November 7th in New York City, NY (with optional training day on Nov. 6th) and November 9th in Chicago, IL.

2Q PGConf is a conference dedicated to exchanging knowledge about PostgreSQL and helping you to understand how it can work for your enterprise or business.

2Q PGConf provides a unique opportunity to learn more about PostgreSQL from world-class experts talking about both recent achievements and the exciting developments coming in the future.

In addition to the world class talks being presented in New York and Chicago - we are also offering training sessions the day before the conference in New York (Nov. 6) in the following areas: Postgres-BDR, Postgres-XL & Performance, and PostgreSQL 10 New Features.

For more details about 2Q PGConf 2017, please visit http://www.2qpgconf.com/#about

Call for Papers

Call for Papers is officially open! We are looking for dynamic presentations, case studies, and talks on the following topics:

• PostgreSQL 10
• PostgreSQL 11 - What's in store for the future of PostgreSQL?
• Administering large scale PostgreSQL installations
• Case studies and/or success stories of PostgreSQL deployments (or interesting failures)
• PostgreSQL tools and utilities
• Community and local user groups
• Tuning and performance improvements
• Migration from other database systems
• Replication, Clustering and High Availability
• Disaster Recovery and Backup strategies
• Benchmarking and hardware
• DevOps and continuous deployment/configuration/integration around PostgreSQL

This list is not exhaustive, we would love to receive any interesting submissions surrounding PostgreSQL.

For a full list of topics or to submit a talk, visit http://www.2qpgconf.com/#cfp

Submission deadline is midnight August 22, 2017 Pacific Time.

Sponsorship

Want to be a part of the Open Source PostgreSQL movement? Join us as a sponsor of 2Q PGConf 2017! Read about sponsorship opportunities at http://www.2qpgconf.com/#sponsors

Important Dates

• 25 July 2017 - CFP Opens
• 22 Aug 2017 - CFP Closes
• 5 Sept 2017 - Speakers are informed of talk acceptance

For any additional questions or information about 2Q PGConf, please contact 2QPGConf@2ndQuadrant.com

Paris, France - July 24th, 2017

ldap2pg is a simple yet powerful tool to synchronize Postgres roles and ACLs from LDAP directories, including OpenLDAP and Active Directory.

Project goals include stability, portability, high configurability, state of the art code quality and nice user experience.

Here is what's new in version 2.0:

Inspect, grant and revoke custom ACLs.
Reassign objects on role delete.
Manage several databases.
Move to libldap through pyldap.
Accept standard libldap LDAP* env vars.
Deprecation: LDAP_* envvars are deprecated in favor of libldap2 regular envvars.
Read ldaprc files.
SSL/TLS support.
SASL authentification support.
Read configuration from stdin.

Here is some documentation to learn more about Ldap2pg: https://ldap2pg.readthedocs.io/en/latest/

Contribution: Check out our Github repository and help us if you can

Oxford, United Kingdom - July 17, 2017

2ndQuadrant is proud to announce the release of Barman 2.2. Barman is a Backup and Disaster Recovery Manager for PostgreSQL databases.

This major release boasts a long awaited feature: the implementation of parallel copy for backup/recovery through the parallel_jobs option. This highly anticipated feature allows Barman to perform copies at an accelerated rate, speeding up the backup and recovery process for the rsync copy method.

Subito, long time partners of 2ndQuadrant and sponsors of the Barman project, were happy to participate in early testing of the parallel copy feature. The Subito Data Team was pleased with the results, stating that "Barman's parallel backup feature with 4 parallel jobs doubled transfer rate and cut the backup time by 60% and recovery time by 40%."

This feature has been a goal of the development team for some time. "Parallel copy fills an important gap for Barman in very large database (VLDB) scenarios, by giving users flexibility and freedom in architecture design to help them reduce both backup and recovery times sensibly," said Gabriele Bartolini, one of the lead developers behind Barman. "This feature takes advantage of the code refactoring activity that has been previously performed with 2.0 and 2.1 releases, including the thousands of automated tests that help us make Barman more robust."

Other notable features in this major release include:

• Support custom WAL size (PostgreSQL 8.4 and up)
• Improve check command
• Add external_configuration to backup_options
• Add --get-wal and --no-get-wal options to barman recover
• Add max_incoming_wals_queue global/server option for the check command
• Documentation improvements

Additionally, several minor bug fixes have also been implemented. Read the full release notes for Barman 2.2 here.

Navionics, manufacturer of electronic navigational charts and founding sponsor of the Barman project, migrated its systems to PostgreSQL in 2012. With several servers under Barman backup, the Navionics team stated that they are proud to have contributed again in the developing of a new Barman release that includes parallel jobs. "We have been a sponsor of Barman since the first release because we need a reliable system and disaster recovery [capability] for our production servers," stated the Navionics DBA Team. "We are sure that [parallel copy within Barman] will allow us to have faster backup and restore for our huge databases."

About Barman

Barman is an open-source administration tool for backup and disaster recovery of PostgreSQL servers written in Python. It allows organizations to perform remote backups of multiple servers in business critical environments and help DBAs during the recovery phase.

Barman is developed and maintained by 2ndQuadrant and distributed under GPL v3.

To learn more about Barman please visit https://www.2ndquadrant.com/en/resources/barman/.

About 2ndQuadrant

2ndQuadrant was founded in 2001 by Simon Riggs, a major developer and committer of the PostgreSQL project. As the largest single collective organization of PostgreSQL experts of any company globally, it is 2ndQuadrant's mission to provide the gold standard of products and services to support PostgreSQL and its continuous growth. Comprised of some of the best known developers from around the globe, all members actively contribute to the development of PostgreSQL.

The PostgreSQL Global Development Group announces today that the second 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 first beta. Users are encouraged to begin testing their applications against 10 beta2.

Upgrading to Beta2

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

Changes Since Beta1

Any bugfixes applied to 9.6 or earlier that also affected 10 are included in beta2. Our users and contributors also reported bugs against 10 beta 1, 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:

• Fix memory leaks in new partitioning code
• Don’t explicitly mark range partitioning columns as NOT NULL
• Fix compilation with BSD authentication
• Try next host after timeout in libpq with multiple hosts specified
• Verify that the server constructed SCRAM none correctly
• Fix table sync in logical replication for tables with columns in different order
• Fix pg_dump:ing collations from pre-10 servers
• Fix crash in BRIN index auto summarization
• Generate pg_basebackup temporary slot name from backend pid, not client
• Make ALTER SEQUENCE fully transactional
• Allow COPY (query) TO to be parallelized
• Fix ALTER SUBSCRIPTION grammar ambiguity
• Don’t set application_name in logical replication workers
• Allow query cancel of walsender backends
• Prevent BEFORE triggers from violating partition constraints
• Mark to_tsvector(regconfig, json[b]) functions as immutable
• Apply RLS policies to partitioned tables
• Add MSVC build system support for ICU and fix ICU support on Windows
• Disallow set returning functions inside CASE or COALESCE
• Teach PL/pgSQL about partitioned tables
• Don’t downcase entries in shared_preload_libraries et al
• Prevent table partitions from being turned into views
• Fix IF NOT EXISTS in CREATE STATISTICS
• Fix memory leaks in in ICU encoding conversion
• Fix import of system collations
• Fix logical replication with replication identity full
• Support tcp_keepalive_idle option on Solaris
• Don’t require schema public to exist for pg_dump -c
• Fix transition tables for partition/inheritance, writable CTEs and ON CONFLICT
• Change pg_ctl -w to detect server-ready state by watching status in postmaster.pid
• Forbid gen_random_uuid() when built with --disable-strong-random
• Allow libpq to use multiple hostaddrs to go with multiple hostnames
• Fix COPY handling of transition tables with indexes
• On Windows, retry process creation in case shared memory reservation fails

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 second 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

Paris, France - July 5th, 2017

ldap2pg is a simple yet powerful tool to synchronize Postgres roles from LDAP directories, including OpenLDAP and Active Directory. Version 1.0 was released today, and there's more to come!

Project goals include stability, portability, high configurability, state of the art code quality and nice user experience.

Highlighted features

Configure multiples LDAP queries.
Customize Postgres role options (LOGIN, SUPERUSER, REPLICATION, etc.).
Create, alter and drop roles.
Manage role members.
Dry run to audit a cluster.

Here is some documentation to learn more about Ldap2pg: https://ldap2pg.readthedocs.io/en/latest/

It has been a while since the last release of PgBackMan and with this version we hope to start a new period with more frequent releases. This new release implements some new features and fixes some bugs from version 1.1.0. Source files, RPM and DEB files are available at GitHub.

New features

• Add dbname exception field to "register snapshot definition"
• Add dbname exception field to "register backup definitions"
• Possibility of defining multiple snapshots definitions in one command
• Update "show pgbackman config" to show more information
• Define a default backup server in all backup servers inputs.
• Possibility of generating CSV and JSON output with all show_* pgbackman commands
• Refactor the code used to manage command line parameters and define new parameters.
• Automatic compression of cluster type backups if gzip is available.
• New command to move backup definitions between backup servers.
• Add support for postgreSQL 9.6

Migration to 1.2.0

It is very important to check the upgrade procedure to version 1.2.0 in the documentation to avoid problems and errors when and after upgrading to the new version.

Check the section "Upgrading PgBackMan" for more information.

Bugfixes

• "show job queues" view does not show the right domain for pgsql_nodes. Issue:#47
• Backup definitions of type CLUSTER getting DELETE status. Issue:#39

PL/Java brings functions, triggers, and types in Java. 1.5.1, now in beta, adds support for PostgreSQL 9.6 and 10 (beta), with a small number of improvements and fixes.

Project site: http://tada.github.io/pljava/
Release notes: http://tada.github.io/pljava/releasenotes.html

Security note

One previously-announced security issue is addressed in PL/Java 1.5.1, as described in the release notes.

Selected changes

This release introduces support for parallel-safety declarations on functions in PostgreSQL 9.6. Simple cases work as expected, but PL/Java's code has not been thoroughly audited to be sure its internal behavior cannot violate constraints on parallel-restricted or parallel-safe functions. See the release notes and new user-guide page on parallel query. This could be a fruitful area for beta testing.

In PostgreSQL 10, trigger transition tables are supported for AFTER triggers, as described in the release notes.

Notable changes have also been made for the benefit of maintainers of prebuilt PL/Java packages for software distributions. They allow the build to be tailored appropriately with options on the mvn command line and no need to patch the source. One of these allows a working default for pljava.libjvm_location to be built in, when packaging for a distribution that has a known, conventional location for Java. An entire section for package maintainers has been added to the build docs.

Please see the release notes for a more complete list of changes.

Availability

1.5.1-BETA1 is available from GitHub as a source release, which builds quickly using Maven:

Release page: https://github.com/tada/pljava/releases/tag/V1_5_1b1

This wiki page will add links to prebuilt packages that become available:
https://github.com/tada/pljava/wiki/Prebuilt-packages

PostgreSQL Conference Europe 2017 will be held on October 24-27 in the Warsaw Marriott Hotel, in Warsaw, Poland. It will cover topics for PostgreSQL users, developers and contributors, as well as decision and policy makers. For more information about the conference, please see the website.

If you are interested in our sponsorship opportunities, please see the end of this announcement.

We are now accepting proposals for talks in English.

Each session will last 45 minutes, and may be on any topic related to PostgreSQL. Suggested topic areas include:

• Developing applications for PostgreSQL
• Administering large scale PostgreSQL installations
• Case studies and/or success stories of PostgreSQL deployments
• PostgreSQL tools and utilities
• PostgreSQL hacking
• Community & user groups
• Tuning the server
• Migrating from other systems
• Scaling/replication
• Benchmarking & hardware
• PostgreSQL related products

Of course, we're happy to receive proposals for talks on other PostgreSQL related topics as well.

We may also have a limited number of longer, 90-minute, slots available. Please indicate clearly in your submission if you wish to make a 90-minute talk.

Finally, there will be a session of five minute lightning talks. A separate call for proposals will be made for them further on.

The submission deadline is August 7th. Selected speakers will be notified before August 22nd, 2017.

Please submit your proposals by going to the submission system and following the instructions there.

The proposals will be considered by committee who will produce a schedule to be published nearer the conference date.

All selected speakers will get free entry to the conference (excluding training sessions). We do not in general cover travel and accommodations for speakers, but may be able to do so in limited cases. If you require assistance with funding to be able to attend, please make a note of this in the submission notes field.

We have also opened our Call for Sponsors. We offer a wide range of sponsorship opportunities, ranging from a low cost Bronze level which is a great way to show your support for the community, to the Platinum level which is limited to three sponsors (so act fast if you are interested!).

If you are interested, please see the detailed descriptions and click the signup link from there!

We look forward to hearing from you, and seeing you in Warsaw in October!

check_pgactivity 2.2 released

The OPMDG has finally released the version 2.2 of check_pgactivity. Most of the changes were already committed since a long time, but this release finally brings official support for PostgreSQL 9.6 in check_pgactivity.

This release brings some new features :

• support for PostgreSQL 9.6
• add service sequences_exhausted to prevent a sequence running out of ids
• add service stat_snapshot_age to detect a stuck stats collector process
• add service pgdata_permission to monitor rights and ownership of PGDATA directory
• add support for "pending restart" parameters in service settings (9.5+)
• add timeline of in the perfdata output in service wal_files
• add warn/critical thresholds to streaming_delta perfdata
• make thresholds optional in service streaming_delta

Some fixes and changes were also done :

• fix backends_status for PostgreSQL 9.6
• improve and rename "ready_archives" to "archiver"
• fix archive_folder to handle compressed archived WAL properly
• fix a race condition to handle concurrent executions correctly
• fix bug in "human" output format
• fix documentation about default db connection
• now use parameter server_version_num to detect PostgreSQL version

What is check_pgactivity

check_pgactivity is a Nagios-compatible checker to monitor every key features of a PostgreSQL cluster :

• number of sessions, longuest queries, locked sessions, etc
• database size, bloated tables and bloated indexes
• WAL files, archiver state, database dumps
• streaming replication, replication slots
• and many more

check_pgactivity supports several output formats :

• Nagios, strict or not
• Human-readable
• binary (Perl-compatible)

Why check_pgactivity ?

The OPMDG was initially formed by Dalibo to support the development of our OPM monitoring suite. The OPMDG is an informal group of people contributing to OPM and related tools, and is independant from the company in order to encourage other contributors to submit patches.

We initially thought about using check_postgres for the OPM monitoring suite, but it lacked some crucial performance datas and the base code was difficult to maintain. We decided to write our own Nagios checker from scratch, in a more maintainable manner and with a focus on a rich perfdata set.

Thus, it's now very easy to extend check_pactivity to support new services or simply support a new PostgreSQL release - PostgreSQL 10 support is already in the work. The output format is automatically treated by check_pgactivity, a service just has to return a some variables.

Download

All releases can by downloaded from github : https://github.com/OPMDG/check_pgactivity/releases

The project page : https://github.com/OPMDG/check_pgactivity

Database .NET v22 is an innovative, powerful and intuitive multiple database management tool. (Full support for PostgreSQL 8.4~9.6)

Free, All-In-One, Portable, Single executable file and Multi-language.

Major New features from version 19.9 to 22.0:

• Updated to Npgsql.dll 3.2.2
• Massive performance improvements (>30%+)
• Added support for Asynchronous connection open
• Added support for PostgreSQL Extension objects
• Added support for PostgreSQL Exclusion Constraints
• Added generating CRUD stored procedures for PostgreSQL
• Added displaying RefCursor results for PostgreSQL
• Added displaying Indexes for PostgreSQL Materialized Views
• Added automatically list foreign key references to IntelliSense
• Added auto Commit to Context Menu
• Added generating INSERTs to new query window
• Added full screen results
• Added preserving NULL values by Exporting and Importing delimited text files
• Added generating Delimited text files by Script Generator
• Added support for importing XML format
• Added support for exporting data to Markdown format
• Added syntax Validation for creating a new table
• Ability to delete multiple selected objects
• ...and more

For more information please visit http://fishcodelib.com/Database.htm.

Intelligent Converters released new versions of MSSQL-to-PostgreSQL and Oracle-to-PostgreSQL with the following enhancements:

• option to convert views in PostgreSQL format
• option to export into PostgreSQL script file
• improved support for Azure SQL (in MSSQL-to-PostgreSQL)

PostgresOpen and PGConf SV have joined forces this year to put together a fantastic PostgreSQL conference, PostgresOpen SV 2017, being held in
downtown San Francisco from September 6th to 8th.

Early Bird Registration for PostgresOpen SV 2017 is now open!

Simply go to our tickets page and register to attend the longest running annual PostgreSQL conference in the US.

The Program Committee is excited to be able to offer tickets for PostgresOpen SV at the same rate as last year, with a $200 discount for early bird registrations!

We also want to remind you that the Call for Papers is only open until May 30th, Anywhere on Earth (AoE), this is the last chance for you to submit your talk for PostgresOpen SV 2017, there's only two weeks left!

Presentations on any topic related to PostgreSQL including, but not limited to, case studies, experiences, tools and utilities, application development, data science, migration stories, existing features, new feature development, benchmarks, and performance tuning are encouraged.

Tutorials will be announced in the coming weeks- watch our blog for updates!

The Program Committee looks forward to bringing the best PostgreSQL presentations and tutorials from speakers around the world to the fantastic Parc55 in downtown San Francisco.

Speakers will be notified by June 6th, 2017 AoE, with the schedule to be published once selected speakers have confirmed.

PostgresOpen SV 2017 is only able to happen with the support of our fantastic sponsors. We are extremely pleased to be able to recognize our Diamond launch sponsors:

2ndQuadrant

CitusData

and head to our site to see all of our Gold, Silver and Supporter sponsors

Sponsorship opportunities are still available!

We look forward to seeing everyone in San Francisco!

Any questions? Please contact: program2017@postgresopen.org