The PostgreSQL Global Development Group announces today that the first beta release of PostgreSQL 9.6 is available for download. This release contains previews of all of the features which will be available in the final release of version 9.6, although some details will change before then. Users are encouraged to begin testing their applications against this latest release.

Major Features of 9.6

Version 9.6 includes significant changes and exciting enhancements including:

• Parallel sequential scans, joins and aggregates
• Support for consistent, read-scaling clusters through multiple synchronous standbys and "remote_apply" synchronous commit.
• Full text search for phrases
• postgres_fdw can now execute sorts, joins, UPDATEs and DELETEs on the remote server
• Decreased autovacuum impact on big tables by avoiding "refreezing" old data.

In particular, parallel execution should bring a noticeable increase in performance to supported queries.

Help Test for Bugs

As with other major releases, the improvements in PostgreSQL include changes to large amounts of code. We count on you to test the altered version with your workloads and testing tools in order to find bugs and regressions before the release of PostgreSQL 9.6.0. In addition to testing that the new features work as documented, consider testing the following:

• Do parallel queries actually improve performance for you?
• Can you make parallel queries crash or lose data?
• Do our code changes cause PostgreSQL to not function on your platform?
• Does improved vacuum freezing safely reduce autovacuum of large tables?
• Does phrase search return the results you expect?

Version 9.6 Beta 1 also makes changes to the binary backup API. Administrators should test version 9.6 with PostgreSQL backup tools, including pgBackRest, Barman, WAL-E, and other packaged and in-house software.

As this is a Beta, minor changes to database behaviors, feature details, and APIs are still possible. Your feedback and testing will help determine the final tweaks on the new features, so test soon. The quality of user testing helps determine when we can make a final release.

Beta Schedule

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

Links

• Downloads Page
• Beta Testing Information
• 9.6 Beta Release Notes
• What's New in 9.6
• 9.6 Open Items

2ndQuadrant, the leading developers of PostgreSQL, are delighted to announce the release of pglogical 1.1 – the next generation in replication systems for PostgreSQL.

The 1.1 release brings new features along with bug fixes to pglogical. Same salient features are listed below:

• Sequence replication support
• Support for replica triggers
• Foreign keys are no longer checked on the replica
• Multiple subscriptions between single pair of nodes
• The create_subscription function does not synchronize structure change by default
• User can specify affected replication sets in replicate_ddl_command function
• New functions for manipulating connection strings of nodes
• PGLogical processes are clearly marked in the pg_stat_activity
• Better behavior on worker crashes
• Logging improvements
• Ubuntu Xenial package

pglogical offers Logical Replication as a PostgreSQL extension, which provides the flexibility of trigger-based replication with the efficiency of log-based replication. This ground-breaking new technology has benefits for many key use cases

• UPGRADE Upgrade PostgreSQL from 9.4 to 9.5, without downtime
• SCALE OUT Copy all or a selection of database tables to other nodes in a cluster
• AGGREGATE Accumulate changes from sharded database servers into a Data Warehouse
• INTEGRATE Feed database changes in real-time to other systems

pglogical is open source and available for download as binary packages for PostgreSQL 9.4 and 9.5 versions. Visit http://2ndquadrant.com/pglogical/ for more detail.

2ndQuadrant’s respected 24/7 Production Support provides the fastest and highest rated response service for PostgreSQL anywhere and is available now worldwide.

2ndQuadrant leads the drive for improving the enterprise functionality for PostgreSQL, contributing major features every year in performance, replication, business intelligence and usability.

The Postgres-XL community is pleased to announce the 1st release of Postgres-XL 9.5. This release has been fully synced up till PostgreSQL 9.5.2.

Postgres-XL is a massively parallel database built on top of, and very closely compatible with PostgreSQL 9.5 and its set of advanced features. Postgres-XL is fully open source and many parts of it will feed back directly or indirectly into later releases of PostgreSQL, as we begin to move towards a fully parallel sharded version of core PostgreSQL.

Postgres-XL is different because it supports both Business Intelligence and OLTP workloads in the same horizontally scalable server. This allows Postgres-XL to support a diverse range of workloads

• OLTP workloads that need write-scalability as well as read-scalability
• Business Intelligence requiring OLAP with massive parallelism
• Operational Data Store/ Central Data Backbone
• Distributed Key-Value store using JSONB, similar to NoSQL
• Internet of Things applications
• Mixed-workload environments

Star schema style SQL queries exhibit large performance gains from massively parallel processing (MPP). Many queries show fully linear performance gains, for example a 16-node XL cluster is 16 times faster than PostgreSQL on one node. Postgres-XL is able to successfully complete the complex TPC-H business intelligence benchmark, showing its capability to address much more than basic operations.

Besides proving its mettle on Business Intelligence workloads, Postgres-XL has performed remarkably well on OLTP workloads when running pgBench (based on TPC-B) benchmark. In a 4-Node (Scale: 4000) configuration, compared to PostgreSQL, XL gives up to 230% higher TPS (-70% latency comparison) for SELECT workloads and up to 130% (-56% latency comparison) for UPDATE workloads. Yet, it can scale much, much higher than even the largest single node server.

Postgres-XL’s High Availability functionality has also been enhanced in this release. Popular features such as BRIN indexes, JSONB and GIN index compression are fully supported, as are many popular extensions.

Postgres-XL is available for download here: www.postgres-xl.org/download/ You can go through XL’s comprehensive documentation here: files.postgres-xl.org/documentation/

We expect R2 to bring further features to Postgres-XL 9.5 in the next few months.

2ndQuadrant has led the development of Postgres-XL 9.5, building upon the work of many others over a long period of continuous development, with easily more than 10 man years of development. After six months of professional formal alpha-level testing & tuning, and an additional 2 months in Beta phase with user feedback, the project has now reached the next stage of maturity and we are now ready to release it for production use.

The research leading to these results has received funding from the European Union’s Seventh Framework Programme (FP7/2007-2015) under grant agreement n° 318633. Postgres-XL has also received support and assistance from European Space Agency's Gaia project, as well as other users in industry.

For more details, please visit: 2ndQuadrant.com/resources/postgres-xl/

Greetings!

The Call For Papers for PostgresOpen 2016, being held in Dallas, Texas from September 13th to 16th, is now open!

If you are working with PostgreSQL, please visit:

https://2016.postgresopen.org/callforpapers/

and submit a talk!

Presentations can be on any topic related to PostgreSQL, including, but not limited to, case studies, experiences, tools and utilities, migration stories, existing features, new feature development, benchmarks, performance tuning, and more!

The 2016 PostgresOpen Committee looks forward to bringing the best PostgreSQL presentations and tutorials from speakers around the world to Dallas, Texas! We're only able to do that with support from our great sponsors! If you are interested in sponsoring, please visit our sponsoring campaign:

https://2016.postgresopen.org/becomesponsor/

Anyone and everyone in the PostgreSQL community is encouraged to submit a talk. Talks will be accepted up until May 30th, Anywhere on Earth (AoE), also known as: 2015-05-30 23:59:59-12:00.

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

Early Bird registration for PostgresOpen 2016 will open on May 9th!

Join us in celebrating our 6th conference year! We look forward to seeing everyone in Dallas!

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

Stephen Frost

PostgresOpen 2016 Committee Chair

http://2016.postgresopen.org

April 17, 2016: Crunchy Data is proud to announce pgBackRest 1.0, Reliable PostgreSQL Backup & Restore.

Release 1.0

The first stable of release of pgBackRest introduces a new, more capable repository format, simpler configuration, and comprehensive support for backup and restore of symlinked directories and files.

There are a number of important changes in pgBackRest 1.0 so be sure to read the release notes very carefully before upgrading.

Links

• Website
• Download
• Release Notes
• Documentation
• User Guide
• Support

Features

Multithreaded Backup & Restore

Compression is usually the bottleneck during backup operations but, even with now ubiquitous multi-core servers, most database backup solutions are still single-threaded. pgBackRest solves the compression bottleneck with multithreading.

Utilizing multiple cores for compression makes it possible to achieve 1TB/hr raw throughput even on a 1Gb/s link. More cores and a larger pipe lead to even higher throughput.

Local or Remote Operation

A custom protocol allows pgBackRest to backup, restore, and archive locally or remotely via SSH with minimal configuration. An interface to query PostgreSQL is also provided via the protocol layer so that remote access to PostgreSQL is never required, which enhances security.

Full, Incremental, & Differential Backups

Full, differential, and incremental backups are supported. pgBackRest is not susceptible to the time resolution issues of rsync, making differential and incremental backups completely safe.

Backup Rotation & Archive Expiration

Retention polices can be set for full and differential backups to create coverage for any timeframe. WAL archive can be maintained for all backups or strictly for the most recent backups. In the latter case WAL required to make older backups consistent will be maintained in the archive.

Backup Integrity

Checksums are calculated for every file in the backup and rechecked during a restore. After a backup finishes copying files, it waits until every WAL segment required to make the backup consistent reaches the repository.

Backups in the repository are stored in the same format as a standard PostgreSQL cluster (including tablespaces). If compression is disabled and hard links are enabled it is possible to snapshot a backup in the repository and bring up a PostgreSQL cluster directly on the snapshot. This is advantageous for terabyte-scale databases that are time consuming to restore in the traditional way.

All operations utilize file and directory level fsync to ensure durability.

Backup Resume

An aborted backup can be resumed from the point where it was stopped. Files that were already copied are compared with the checksums in the manifest to ensure integrity. Since this operation can take place entirely on the backup server, it reduces load on the database server and saves time since checksum calculation is faster than compressing and retransmitting data.

Streaming Compression & Checksums

Compression and checksum calculations are performed in stream while files are being copied to the repository, whether the repository is located locally or remotely.

If the repository is on a backup server, compression is performed on the database server and files are transmitted in a compressed format and simply stored on the backup server. When compression is disabled a lower level of compression is utilized to make efficient use of available bandwidth while keeping CPU cost to a minimum.

Delta Restore

The manifest contains checksums for every file in the backup so that during a restore it is possible to use these checksums to speed processing enormously. On a delta restore any files not present in the backup are first removed and then checksums are taken for the remaining files. Files that match the backup are left in place and the rest of the files are restored as usual. Since this process is multithreaded, it can lead to a dramatic reduction in restore times.

Advanced Archiving

Dedicated commands are included for both pushing WAL to the archive and retrieving WAL from the archive.

The push command automatically detects WAL segments that are pushed multiple times and de-duplicates when the segment is identical, otherwise an error is raised. The push and get commands both ensure that the database and repository match by comparing PostgreSQL versions and system identifiers. This precludes the possibility of misconfiguring the WAL archive location.

Asynchronous archiving allows compression and transfer to be offloaded to another process which maintains a continuous connection to the remote server, improving throughput significantly. This can be a critical feature for databases with extremely high write volume.

Tablespace & Link Support

Tablespaces are fully supported and on restore tablespaces can be remapped to any location. It is also possible to remap all tablespaces to one location with a single command which is useful for development restores.

File and directory links are supported for any file or directory in the PostgreSQL cluster. When restoring it is possible to restore all links to their original locations, remap some or all links, or restore some or all links as normal files or directories within the cluster directory.

Compatibility with PostgreSQL >= 8.3

pgBackRest includes support for versions down to 8.3, since older versions of PostgreSQL are still regularly utilized.

About

pgBackRest aims to be a simple, reliable backup and restore system that can seamlessly scale up to the largest databases and workloads. Instead of relying on traditional backup tools like tar and rsync, pgBackRest implements all backup features internally and uses a custom protocol for communicating with remote systems. Removing reliance on tar and rsync allows for better solutions to database-specific backup challenges. The custom remote protocol allows for more flexibility and limits the types of connections that are required to perform a backup which increases security.

Crunchy Data supports the ongoing and active development of pgBackRest as an entirely open source project, released under the BSD-compatible MIT license.

April 8, 2016 – Amazon RDS for PostgreSQL now supports major version 9.5, which contains several new features including UPSERT capability, Row Level Security (RLS) and several Big Data capabilities. In addition to supporting the new major version of PostgreSQL, 9.5, RDS for PostgreSQL also supports new minor versions 9.4.7 and 9.3.12, which contain several enhancements and fixes. All three versions are available to use starting today.

PostgreSQL 9.5 (supported via minor version 9.5.2) offers the following new features:

UPSERT: Shorthand for "INSERT, ON CONFLICT UPDATE", this feature allows new and updated rows to be treated the same way, enabling the database to handle conflicts between concurrent data changes and simplifying application development. Row Level Security (RLS): RLS implements true per-row and per-column data access control which integrates with external label-based security stacks, giving you more control over securing your data. Big Data features: PostgreSQL 9.5 includes multiple new features for integrating with Big Data systems, including BRIN Indexing to create tiny but effective indexes for "naturally ordered" tables; faster sorts using "abbreviated keys" algorithm to sort through text and NUMERIC fields faster; CUBE, ROLLUP and GROUPING SETS to produce reports with multiple levels of summarization to allow integration with OLAP tools such as Tableau; Foreign Data Wrappers (FDWs) with IMPORT FOREIGN SCHEMA and JOIN pushdown to make query connections to external databases easier and more efficient; and TABLESPACE to generate a statistical sample of huge tables to avoid expensive sorting. You can create a new PostgreSQL 9.5.2 database instance with a few clicks on the AWS Management Console (learn how). You may also upgrade an existing PostgreSQL 9.4 instance to version 9.5.2 using major version upgrade. If you wish to upgrade from version 9.3 to 9.5, you will have to perform point-and-click upgrade twice. Each upgrade operation involves a short period of unavailability for your database instance. Learn more about upgrading your database instances.

In addition to PostgreSQL 9.5.2, we also now support PostgreSQL 9.4.7 and 9.3.12, which include several fixes and enhancements as listed here. To learn more about these new versions, please refer to their release notes:

Release Notes for 9.5.2

Release Notes for 9.4.7

Release Notes for 9.3.12

All three versions also now provide visibility into the status of autovacuum by allowing rds_superuser access to autovacuum sessions in pg_stat_activity. Read more about the new features in PostgreSQL 9.5 on the PostgreSQL website. For more details on using Amazon RDS for PostgreSQL, please refer to the Amazon RDS User's Guide.

Amazon RDS

Amazon Relational Database Service (Amazon RDS) makes it easy to set up, operate, and scale a relational database in the cloud. It provides cost-efficient and resizable capacity while managing time-consuming database administration tasks, freeing you up to focus on your applications and business.

Contact:

Kevin Jernigan

Product Manager, RDS for PostgreSQL

+1-415-710-8828

kmj (at) amazon (dot) com

I am proud to announce the 1.3.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 version mainly adds some functions to protect "tables groups" and "marks" from unattended "E-maj rollbacks". The E-Maj phpPgAdmin plugin has been improved as well to use these new features.

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

There is only 1 week left until one of the biggest PostgreSQL events in the world: PGConf US 2016, which is in New York from April 18th to 20th: http://www.pgconf.us/2016/schedule/

Some highlights:

• A keynote presented by Parag Goradia, Executive Director, Cloud Services Engineering, GE Digital
• An awesome set of general sessions on April 19th - 20th
• The Regulated Industry Summit on April 18th (free with regular conference pass!)
• Training sessions from seasoned Postgres trainers!
• A chance to meet fun people from all over the world

…and the biggest PostgreSQL party of the year - come celebrate the PostgreSQL community turning 20! You can signup for the 20th Anniversary Party separately here: http://www.meetup.com/postgresql-3/events/229101241/

Hope to see you at the conference!

The PostgreSQL Global Development Group has released an update to all supported versions of our database system, including 9.5.2, 9.4.7, 9.3.12, 9.2.16, and 9.1.21. This release fixes two security issues and one index corruption issue in version 9.5. It also contains a variety of bug fixes for earlier versions. Users of PostgreSQL 9.5.0 or 9.5.1 should update as soon as possible.

Security Fixes for RLS, BRIN

This release closes security hole CVE-2016-2193, where a query plan might get reused for more than one ROLE in the same session. This could cause the wrong set of Row Level Security (RLS) policies to be used for the query.

The update also fixes CVE-2016-3065, a server crash bug triggered by using pageinspect with BRIN index pages. Since an attacker might be able to expose a few bytes of server memory, this crash is being treated as a security issue.

Abbreviated Keys and Corrupt Indexes

In this release, the PostgreSQL Project has been forced to disable 9.5's Abbreviated Keys performance feature for many indexes due to reports of index corruption. This may affect any B-tree indexes on TEXT, VARCHAR, and CHAR columns which are not in "C" locale. Indexes in other locales will lose the performance benefits of the feature, and should be REINDEXed in case of existing index corruption. The feature may be re-enabled in future versions if the project finds a solution for the problem. See the release notes, and the wiki page on this issue for more information.

Other Fixes and Improvements

In addition to the above, many other issues were patched in this release based on bugs reported by our users over the last few months. This includes bugs which affect multiple versions of PostgreSQL, such as:

• Fix two bugs in indexed ROW() comparisons
• Avoid data loss due to renaming files
• Prevent an error in rechecking rows in SELECT FOR UPDATE/SHARE
• Fix bugs in multiple json_ and jsonb_ functions
• Log lock waits for INSERT ON CONFLICT correctly
• Ignore recovery_min_apply_delay until reaching a consistent state
• Fix issue with pg_subtrans XID wraparound
• Fix assorted bugs in Logical Decoding
• Fix planner error with nested security barrier views
• Prevent memory leak in GIN indexes
• Fix two issues with ispell dictionaries
• Avoid a crash on old Windows versions
• Skip creating an erroneous delete script in pg_upgrade
• Correctly translate empty arrays into PL/Perl
• Make PL/Python cope with identifier names

This update also contains tzdata release 2016c, with updates for Azerbaijan, Chile, Haiti, Palestine, and Russia, and historical fixes for other regions.

Updating

Users of version 9.5 will want to REINDEX any indexes they created on character columns in non-C locales. Users of other versions who have skipped multiple update releases may need to perform additional post-update steps; see the Release Notes for details.

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
• Abbreviated Keys Issue

PL/Java brings functions, triggers, and types in Java. 1.5.0 supports latest PostgreSQL and Java versions with a range of improvements and fixes.

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

Security note:

Several security issues are addressed in PL/Java 1.5.0, as described in the release notes, so sites running earlier versions are encouraged to update. The release notes also describe practical mitigations to reduce risk until an update can be completed.

Platforms:

PL/Java 1.5.0 works with Java 8, 7, or 6 and all 9.x PostgreSQL versions as well as 8.4. To support projects based on older PostgreSQL forks, PL/Java 1.5.0 is also intended to build with 8.3 and 8.2, but has not been tested on those versions.

PL/Java 1.5.0 resolves reported build issues on several platforms, and new sections of the build documentation specifically cover Mac OS X, Solaris, Ubuntu, and Windows (using Visual Studio or MinGW-64). FreeBSD 10.2 or later is expected to work but has not been tested.

Changes:

PL/Java 1.5.0 brings more complete, usable, and documented capability for Java-implemented user-defined base types, composite types, and mirrors of existing PostgreSQL types, an annotation-driven SQL generator reducing the effort of writing deployment SQL by hand, and many smaller improvements and fixes detailed in the release notes. The supplied examples cover many of these features.

Availability:

PL/Java 1.5.0 is available from GitHub as a source release, which builds quickly using Maven:

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

This wiki page will add links to prebuilt packages that become available.

Many thanks to all the individuals and organizations listed in the release notes under Credits.

SQL Maestro Group announces the release of PostgreSQL PHP Generator 16.3, a powerful GUI frontend for Windows that allows you to generate feature-rich CRUD web applications for your PostgreSQL database.

The new version is immediately available at
http://www.sqlmaestro.com/products/postgresql/phpgenerator/.

Live demo and Video tour are available too.

Top 10 new features:

1. Out-of-the-box Charts.
2. Enhanced sidebar menus.
   
3. Compact themes.
4. Embedded Video support.
5. Customizable success/error messages.
6. Enhanced data export tools.
7. Custom form titles.
8. Event management enhancements.
9. Detailed descriptions.
10. PHP configuration settings.

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

I am happy to announce the new major release of Database .NET v18. It is an innovative, powerful and intuitive multiple database management tool, With it you can browse objects, design tables, edit rows, export data, run queries and migrate data with a consistent interface.

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

Major New features from version 17.1 to 18.0:

• Compatible with PostgreSQL 8.4 ~ 9.5+
• Added Visual Execution Plan for PostgreSQL 9.0+
• Massive performance improvements
• Added support for Cancelling executing command
• Added Inspect Object
• Added Dark Mode
• Added support for Renaming Results tab
• Single click for Browsing and Editing
• Improved Data Import and Export
• Improved Data Editor and Browser
• Improved Generating Batch Scripts
• Improved SQL Editor
• Improved AutoComplete and IntelliSense
• Improved SQL File Version Control
• Improved Database Migration and Data Synchronization (Pro)
• ...and more

The new version is immediately available for download.

29 February 2016: 2ndQuadrant is proud to announce the release of version 1.6.0 of Barman, Backup and Recovery Manager for PostgreSQL.

Major release

This major release introduces WAL streaming support, improving disaster recovery capabilities of PostgreSQL backup solutions based on Barman, by reducing Recovery Point Objective consistently to nearly 0. Currently, Barman still requires standard WAL archiving based on PostgreSQL's 'archive_command'. This limitation will be removed once Barman supports replication slots (available from PostgreSQL 9.4).

Barman 1.6.0 introduces also support to pigz compression, as well as Python-native gzip and bzip2 compression algorithms.

Bug fixes

Minor bugs have also been fixed.

For a complete list of changes, see the "Release Notes" section below.

Links

• Website
• Download
• Documentation
• Man page, section 1
• Man page, section 5
• Support
• pgespresso extension

Release notes

• Support for streaming replication connection through the 'streaming_conninfo' server option

• Support for the 'streaming_archiver' option that allows Barman to receive WAL files through PostgreSQL's native streaming protocol. When set to 'on', it relies on 'pg_receivexlog' to receive WAL data, reducing Recovery Point Objective. Currently, WAL streaming is an additional feature (standard log archiving is still required)

• Implement the 'receive-wal' command that, when 'streaming_archiver' is on, wraps 'pg_receivexlog' for WAL streaming. Add '--stop' option to stop receiving WAL files via streaming protocol. Add '--reset' option to reset the streaming status and restart from the current xlog in Postgres.

• Automatic management (startup and stop) of 'receive-wal' command via 'cron' command

• Support for the 'path_prefix' configuration option

• Introduction of the 'archiver' option (currently fixed to 'on') which enables continuous WAL archiving for a specific server, through log shipping via PostgreSQL's 'archive_command'

• Support for 'streaming_wals_directory' and 'errors_directory' options

• Management of WAL duplicates in 'archive-wal' command and integration with 'check' command

• Verify if 'pg_receivexlog' is running in 'check' command when 'streaming_archiver' is enabled

• Verify if failed backups are present in 'check' command

• Accept compressed WAL files in incoming directory

• Add support for the pigz compressor (thanks to Stefano Zacchiroli)

• Implement pygzip and pybzip2 compressors (based on an initial idea of Christoph Moench-Tegeder)

• Creation of an implicit restore point at the end of a backup

• Current size of the PostgreSQL data files in 'barman status'

• Permit 'archive_mode=always' for PostgreSQL 9.5 servers (thanks to Christoph Moench-Tegeder)

• Complete refactoring of the code responsible for connecting to PostgreSQL

• Improve messaging of cron command regarding sub-processes

• Native support for Python >= 3.3

• Changes of behaviour:

  • Stop trashing WAL files during 'archive-wal' (commit:e3a1d16)
• Bug fixes:
  • Atomic WAL file archiving (#9 and #12)
  • Propagate "-c" option to any Barman subprocess (#19)
  • Fix management of backup ID during backup deletion (#22)
  • Improve 'archive-wal' robustness and log messages (#24)
  • Improve error handling in case of missing parameters

Download

• Release Notes
• Sources
• RPMs for RHEL/CentOS 5 (dependencies)
• RPMs for RHEL/CentOS 6 (dependencies)
• PyPI
• pgespresso on PostgreSQL Extension framework (PGXN)
• pgespresso RPM/Debian packages
• Online documentation
• PDF documentation

About

Barman (Backup and Recovery Manager) is an open source administration tool for disaster recovery of PostgreSQL servers written in Python. It allows your organisation to perform remote backups of multiple servers in business critical environments and help DBAs during the recovery phase. Barman's most requested features include backup catalogues, incremental backup, retention policies, remote backup and recovery, archiving and compression of WAL files and backups. Barman is distributed under GNU GPL 3.

Mostly bug fixes and cleanup.

See the changelog for details

The Postgres-XL community is pleased to announce Postgres-XL 9.5 R1 Beta1.

Postgres-XL is a massively parallel database built on top of, and very closely compatible with PostgreSQL 9.5 and its set of advanced features. Postgres-XL is fully open source and many parts of it will feed back directly or indirectly into later releases of PostgreSQL, as we begin to move towards a fully parallel sharded version of core PostgreSQL.

Postgres-XL is different because it supports both Business Intelligence and OLTP workloads in the same horizontally scalable server. This allows Postgres-XL to support a diverse range of workloads

• OLTP workloads that need write-scalability as well as read-scalability
• Business Intelligence requiring OLAP with massive parallelism
• Operational Data Store/ Central Data Backbone
• Distributed Key-Value store using JSONB, similar to NoSQL
• Internet of Things applications
• Mixed-workload environments

Star schema style SQL queries exhibit large performance gains from massively parallel processing (MPP). Many queries show fully linear performance gains, for example a 16-node XL cluster is 16 times faster than PostgreSQL on one node. Postgres-XL is able to successfully complete the complex TPC-H business intelligence benchmark, showing its capability to address much more than basic operations.

Postgres-XL’s High Availability functionality has also been enhanced in this release. Popular features such as BRIN indexes, JSONB and GIN index compression are fully supported, as are many popular extensions.

Postgres-XL is available for download here: http://www.postgres-xl.org/download/ You can go through XL’s comprehensive documentation here: http://files.postgres-xl.org/documentation/index.html

2ndQuadrant has led the development of Postgres-XL 9.5, building upon the work of many others over a long period of continuous development, with easily more than 10 man years of development. After six months of professional formal alpha-level testing and tuning, the project has now reached the next stage of maturity and we are now ready to have initial users contribute their comments and usage reports to the Postgres-XL community at postgres-xl-bugs@lists.sourceforge.net.

The research leading to these results has received funding from the European Union’s Seventh Framework Programme (FP7/2007-2015) under grant agreement n° 318633. Postgres-XL has also received support and assistance from European Space Agency's Gaia project, as well as other users in industry.

For more details, please visit: http://2ndQuadrant.com/resources/postgres-xl/

The PGConf US 2016 schedule is now available:

http://www.pgconf.us/2016/schedule/

PGConf US 2016 is taking place in New York City from April 18th to April 20th at the New York Marriott Brooklyn Bridge. On April 18th, we are pleased to offer six training sessions as well as the Second Annual Regulated Industry Summit, and our usual program on April 19th and 20th.

Did you know that PostgreSQL turns 20 years old this year? We are celebrating by throwing an elephantine (in other words, a gigantic) birthday party for the community on April 19th. The birthday party will be open to the general public and we will have more details on the PGConf US website in the coming days. Come celebrate PostgreSQL turning 20 at PGConf US!

We are pleased to have Parag Goradia, Executive Director of Cloud Services Engineering at General Electric Digital as our keynote speaker at PGConf US 2016. Parag will be discussing how PostgreSQL is playing a crucial role in GE’s software strategy and is looking forward to sharing his story with the community.

And of course, we would not produce PGConf US 2016 without the awesome talks from our speakers. We had just shy of 140 submissions for 44 session slots and 6 and are delighted to present a group of speakers coming from all over the world and volunteering their time to talk about their experiences with PostgreSQL.

Some, but not all, highlights:

• PostgreSQL deployments and strategies at enterprises such as MasterCard, Tencent, Capital One, Blackberry, MongoDB, the European Space Agency, InMobi, and more!
• Want to see what the future of PostgreSQL holds? Come learn how PostgreSQL is developed and how it operates from Major Contributors and PostgreSQL hackers in our internals track.
• Prefer Ruby and Java to SQL? Not a problem: our developer track has you covered so you can learn to take advantage of PostgreSQL’s robustness.

Want to attend? Our registration is open! Please visit http://www.pgconf.us/2016/tickets/ for registration information. Through February 29th 2016, we are offering a 10% discount on the Regular Admission to the global PostgreSQL community with the code PGDG

PGConf US 2016 is hosted by the United States PostgreSQL Association, a nonprofit 501(c)(3) created to support PostgreSQL in the United States through user group development, conferences, educational initiatives, and fun. There is no way we would be able to produce PGConf US 2016 without the generous support of our Platinum and Gold sponsors:

• Platinum: EnterpriseDB, OpenSCG, Citus Data, Compose
• Gold: 2ndQuadrant, Amazon Web Services, PostgreSQL Experts, Pivotal, Braintree

For more information, please visit http://www.pgconf.us/

We look forward to seeing you in April!

Six hundred and eight participants, including sponsors and speakers joined PGCONF.Russia 2016 on Feb.3 - Feb.5.

We invited 21 international and 49 Russian speakers for this conference taking place in Izvestia Hall, Moscow, an untypical venue in the historical city center. Though the main languge of the conference was Russian, simultaneous translation to/from English was provided.

The first day, Feb.3, was a day of 7 tutorials, while other conference activity including conventional and lightning talks, a panel discussion and a conference dinner took place at Deb.4 and Feb.5.

Now we have started publishing slides on the conference website. Video recordings will become available for the conference participants as soon as they are processed, later they will be open for public.

The PgConf.Russia 2016 team members are happy to provide this conference for the Russian and international Postgres community and will do their best to make the next year conference PgConf.Russia 2017 even more interesting. Please follow the announcements at the conference web site https://pgconf.ru/en/ .

The PostgreSQL Global Development Group has released an update to all supported versions of our database system, including 9.5.1, 9.4.6, 9.3.11, 9.2.15, and 9.1.20. This release fixes two security issues, as well as several bugs found over the last four months. Users vulnerable to the security issues should update their installations immediately; other users should update at the next scheduled downtime.

Security Fixes for Regular Expressions, PL/Java

This release closes security hole CVE-2016-0773, an issue with regular expression (regex) parsing. Prior code allowed users to pass in expressions which included out-of-range Unicode characters, triggering a backend crash. This issue is critical for PostgreSQL systems with untrusted users or which generate regexes based on user input.

The update also fixes CVE-2016-0766, a privilege escalation issue for users of PL/Java. Certain custom configuration settings (GUCS) for PL/Java will now be modifiable only by the database superuser.

Other Fixes and Improvements

In addition to the above, many other issues were patched in this release based on bugs reported by our users over the last few months. This includes multiple fixes for new features introduced in version 9.5.0, as well as refactoring of pg_dump to eliminate a number of chronic issues with backing up EXTENSIONs. Among them are:

• Fix many issues in pg_dump with specific object types
• Prevent over-eager pushdown of HAVING clauses for GROUPING SETS
• Fix deparsing error with ON CONFLICT ... WHERE clauses
• Fix tableoid errors for postgres_fdw
• Prevent floating-point exceptions in pgbench
• Make \det search Foreign Table names consistently
• Fix quoting of domain constraint names in pg_dump
• Prevent putting expanded objects into Const nodes
• Allow compile of PL/Java on Windows
• Fix "unresolved symbol" errors in PL/Python execution
• Allow Python2 and Python3 to be used in the same database
• Add support for Python 3.5 in PL/Python
• Fix issue with subdirectory creation during initdb
• Make pg_ctl report status correctly on Windows
• Suppress confusing error when using pg_receivexlog with older servers
• Multiple documentation corrections and additions
• Fix erroneous hash calculations in gin_extract_jsonb_path()

This update also contains tzdata release 2016a, with updates for Cayman Islands, Metlakatla, Trans-Baikal Territory (Zabaykalsky Krai), and Pakistan.

Updating

Users of version 9.4 will need to reindex any jsonb_path_ops indexes they have created, in order to fix a persistent issue with missing index entries. Users of other versions who have skipped multiple update releases may need to perform additional post-update steps; see the Release Notes for details.

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

PL/Java brings functions, triggers, and types in Java. 1.5.0, now in beta, supports latest PostgreSQL and Java versions with a range of improvements and fixes.

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

Security note:

1.5.0 brings a policy change to a more secure-by-default posture, where the ability to create functions in `LANGUAGE java' is no longer automatically granted to 'public', but can be selectively granted to roles that will have that responsibility. The change reduces exposure to a known issue present in 1.5.0 and earlier versions, that will be closed in a future release; details are in the release notes.

The new policy will be applied in a new installation; permissions will not be changed in an upgrade, but any site can move to this policy, even before updating to 1.5.0, with REVOKE USAGE ON LANGUAGE java FROM public; followed by explicit GRANT commands for the users/roles expected to create Java functions. Many sites guided by the principle of least privilege may have chosen such a policy already.

MS Windows note:

1.5.0 development snapshots have been repeatedly tested on Windows building with Visual Studio (including the Express and Community editions), and the build documentation covers this combination. Beta testers should find it straightforward.

Resources have not been available to test MinGW-based builds. Beta testers using this combination are encouraged to report build issues they may encounter. (Patches, where possible, would be appreciated also. A likely place to look in case of issues would be the comments above PLJAVADLLEXPORT in Backend.c.)

Many thanks to all the individuals and organizations listed in the release notes under Credits.

After seven successful sessions dedicated to the new features of PostgreSQL 9.0 (February 2011), to PostGIS (June 2011 & September 2014), to replication systems (February 2012), to migration from Oracle to PostgreSQL (October 2012), to PostgreSQL performance (March 2013) and to our 10th anniversary, in September 2015, we'd like to announce that the 8th PostgreSQL Session will be held on April 6th, 2016, in Lyon, France.

This year, another place, but always the same format!

Indeed, Dalibo and Oslandia organize together one day of lectures dedicated to PostgreSQL and PostGIS.

We're launching a call for papers for this event. You may now submit your talks, in English or in French. Each talk should last 30 minutes (questions included). We are interested in any talks on the following subjects:

PostgreSQL :

• What's New in PostgreSQL
• Use cases
• Migration to PostgreSQL
• Performance Tuning
• Backup and Restore
• High-Availability
• Data Warehouse / Big Data

PostGIS :

• Advanced spatial analysis with PostgreSQL/PostGIS
• PointCloud Data and/or 3D with PostgreSQL/PostGIS
• Performances improvements with PostgreSQL/PostGIS

Talks can be either: a case study, a Proof of Concept, a tutorial, a benchmark, a presentation of a new feature, etc. Of course, we're open to propositions on any other migration related topics (monitoring, hardware, replication, etc.) !

The submission deadline is February 29, 2016.

You can now send your proposals to call-for-paper@postgresql-sessions.org

Please give us a little information about yourself and your talk, such as:

• First Name and Last Name
• Twitter Account (if any)
• Company
• Short Biography (contributions to the PostgreSQL community)
• Talk title
• Talk abstract
• Any specific needs

Slides should have a free licence (Creative Commons BY-ND 3.0 or compatible), and sent to Dalibo. This day will be filmed, and all the lectures will be recorded and published after the Session. By sending a proposal, you agree to be recorded and waive any compensation for it.

The selected speakers not living in France will be reimbursed for travel and one night accomodation.

See you in Lyon in April !

About the PostgreSQL Sessions:

The PostgreSQL sessions are designed to be a time to discover and meet the community. Each session is a single day consisting of lectures, organized around a specific theme and a guest. The proposed talks aimed at all levels and all profiles: Developer, Administrator, Project Managers, IT Managers, ...

Entry is free and open to all, within the limits of available seats.

About Dalibo:

Since 2005, Dalibo is the leading French PostgreSQL company and provides its experience and expertise to its clients in Europe. The company delivers a full range of PostgreSQL services: Training, Development, Performance Tuning, High Availibilty setup, Oracle to PostgreSQL migration, Troubleshooting, and PostgreSQL support.

About Oslandia:

Oslandia is a company with a focus on Open Source GIS architecture. We are characterized by our expertise, agility and dynamism. Our business model is based on services around Open Source GIS software which we are expert on. More than just offering expertise, we are also software editor for some OpenSource GIS components we develop, renown and used worldwide (PostGIS, MapServer Suite, QGIS). This implication requires us to be in the heart of communities of developers and standardisation (worldwide codesprints, participation in future software version orientation, new feature development on our own R&D budgets...).