||Server Applications Technical Updates [Page: 4 of 115] @ TACKtech Corp.
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.
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.
In your postgresql.conf file, add the following:
allow_system_table_mods = true
After adding that line, you will need to restart your PostgreSQL cluster.
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
U.oid AS umid,
S.oid AS srvid,
S.srvname AS srvname,
U.umuser AS umuser,
CASE WHEN U.umuser = 0 THEN
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)
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);
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';
Remove the following line from your postgresql.conf file:
allow_system_table_mods = false
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.
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.
Full View / NID: 67465 / Submitted by: The Zilla of Zuron
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:
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:
Our trainings and sponsored workshops are filling up fast now, be sure to register for the conference and the sessions you're interested in:
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:
And our Platinum sponsor:
Be sure to check out our site to see all of our Gold, Silver and Supporter sponsors, and our Community Partners here:
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!
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:
We look forward to seeing everyone in San Francisco in less than a month!
Any questions? Please contact: firstname.lastname@example.org.
Full View / NID: 67445 / Submitted by: The Zilla of Zuron
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 !
Full View / NID: 67394 / Submitted by: The Zilla of Zuron
The PHP development team announces the immediate availability of PHP 7.2.0 Beta 2. This release is the second beta for 7.2.0. All users of PHP are encouraged to test this version carefully, and report any bugs and incompatibilities in the bug tracking system. THIS IS A DEVELOPMENT PREVIEW - DO NOT USE IT IN PRODUCTION! For more information on the new features and other changes, you can read the NEWS file, or the UPGRADING file for a complete list of upgrading notes. These files can also be found in the release archive. For source downloads of PHP 7.2.0 Beta 2 please visit the download page, Windows sources and binaries can be found at windows.php.net/qa/. The third and final beta will be released on the 17th of August. You can also read the full list of planned releases on our wiki. Thank you for helping us make PHP better.
Full View / NID: 67376 / Submitted by: The Zilla of Zuron
The PHP development team announces the immediate availability of PHP 7.1.8. This is a bugfix release, with several bug fixes included. All PHP 7.1 users are encouraged to upgrade to this version. For source downloads of PHP 7.1.8 please visit our downloads page, Windows source and binaries can be found on windows.php.net/download/. The list of changes is recorded in the ChangeLog.
Full View / NID: 67375 / Submitted by: The Zilla of Zuron
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
- Support Foreign Server with User Mapping.
- Support Foreign Table.
- Support PostgreSQL Debugger.
- 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
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.
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.
Full View / NID: 67296 / Submitted by: The Zilla of Zuron
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.
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
- 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
Full View / NID: 67316 / Submitted by: The Zilla of Zuron
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.
SASL authentification support.
Read configuration from stdin.
Here is some documentation to learn more about Ldap2pg:
Contribution: Check out our Github repository and help us if you can
Full View / NID: 67228 / Submitted by: The Zilla of Zuron
The PHP development team announces the immediate availability of PHP 7.2.0 Beta 1. This release is the first beta for 7.2.0. All users of PHP are encouraged to test this version carefully, and report any bugs and incompatibilities in the bug tracking system. THIS IS A DEVELOPMENT PREVIEW - DO NOT USE IT IN PRODUCTION!PHP 7.2.0 Beta 1 builds on previous releases with:The much anticipated Sodium extensionOpcache improvementsCountable support for DOMNodeList and DOMNamedNodeMapImproved handling for invalid UTF8 in json_decode()And many bugfixes... For more information on the new features and other changes, you can read the NEWS file, or the UPGRADING file for a complete list of upgrading notes. These files can also be found in the release archive. For source downloads of PHP 7.2.0 Beta 1 please visit the download page, Windows sources and binaries can be found at windows.php.net/qa/. The second beta will be released on the 3rd of August. You can also read the full list of planned releases on our wiki. Thank you for helping us make PHP better.
Full View / NID: 67188 / Submitted by: The Zilla of Zuron
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."
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/.
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.
Full View / NID: 67156 / Submitted by: The Zilla of Zuron
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.
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.
Full View / NID: 67111 / Submitted by: The Zilla of Zuron
The PHP development team announces the immediate availability of PHP 7.2.0 Alpha 3. This release contains fixes and improvements relative to Alpha 2. All users of PHP are encouraged to test this version carefully, and report any bugs and incompatibilities in the bug tracking system.THIS IS A DEVELOPMENT PREVIEW - DO NOT USE IT IN PRODUCTION!For information on new features and other changes, you can read the NEWS file, or the UPGRADING file for a complete list of upgrading notes. These files can also be found in the release archive.For source downloads of PHP 7.2.0 Alpha 3 please visit the download page, Windows sources and binaries can be found on windows.php.net/qa/.The first beta will be released on the 20th of July. You can also read the full list of planned releases on our wiki.Thank you for helping us make PHP better.
Full View / NID: 67032 / Submitted by: The Zilla of Zuron
The PHP development team announces the immediate availability of PHP 7.1.7. This is a security release with several bug fixes included. All PHP 7.1 users are encouraged to upgrade to this version. For source downloads of PHP 7.1.7 please visit our downloads page, Windows source and binaries can be found on windows.php.net/download/. The list of changes is recorded in the ChangeLog.
Full View / NID: 67031 / Submitted by: The Zilla of Zuron
The PHP development team announces the immediate availability of PHP 5.6.31. This is a security release. Several security bugs were fixed in this release. All PHP 5.6 users are encouraged to upgrade to this version.For source downloads of PHP 5.6.31 please visit our downloads page, Windows source and binaries can be found on windows.php.net/download/. The list of changes is recorded in the ChangeLog.
Full View / NID: 67030 / Submitted by: The Zilla of Zuron
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.
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:
Full View / NID: 67025 / Submitted by: The Zilla of Zuron
The PHP development team announces the immediate availability of PHP 7.2.0 Alpha 2. This release contains fixes and improvements relative to Alpha 1. All users of PHP are encouraged to test this version carefully, and report any bugs and incompatibilities in the bug tracking system.THIS IS A DEVELOPMENT PREVIEW - DO NOT USE IT IN PRODUCTION!For information on new features and other changes, you can read the NEWS file, or the UPGRADING file for a complete list of upgrading notes. These files can also be found in the release archive.For source downloads of PHP 7.2.0 Alpha 2 please visit the download page, Windows sources and binaries can be found on windows.php.net/qa/.The third and final alpha will be released on the 6th of July. You can also read the full list of planned releases on our wiki.Thank you for helping us make PHP better.
Full View / NID: 66873 / Submitted by: The Zilla of Zuron
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.
- 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.
- "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
Full View / NID: 66870 / Submitted by: The Zilla of Zuron
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
One previously-announced security issue is addressed in PL/Java 1.5.1, as
described in the release notes.
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.
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:
Full View / NID: 66858 / Submitted by: The Zilla of Zuron
The PHP development team announces the immediate availability of PHP 7.1.6. Several bugs have been fixed. All PHP 7.1 users are encouraged to upgrade to this version. For source downloads of PHP 7.1.6 please visit our downloads page, Windows source and binaries can be found on windows.php.net/download/. The list of changes is recorded in the ChangeLog.
Full View / NID: 66681 / Submitted by: The Zilla of Zuron
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
- 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!
Full View / NID: 66660 / Submitted by: The Zilla of Zuron