Very High Activity
I Use This!

News

Analyzed 1 day ago. based on code collected 1 day ago.
Posted 2 months ago
23 May 2016: 2ndQuadrant is proud to announce the release of Barman version 1.6.1, a Backup and Recovery Manager for PostgreSQL. This minor release introduces support for '--peek' option for 'get-wal' command which allows users to implement parallel ... [More] remote restore commands on standby servers and during recovery. Through the new 'replication-status' command, Barman becomes a very practical tool for monitoring streaming replication status of every managed server. A few important improvements have been added to the 'check' command, which should make installation and initial configuration easier. Another step in this direction is the 'switch-xlog' command, a new feature also included in this release. Minor bugs have also been fixed, including support for 'archive_mode=always' for PostgreSQL 9.5, as well as 'FAILED' backups preventing new one from being taken. Many thanks for funding towards the development of this release go to Jobrapido (www.jobrapido.com), Navionics (www.navionics.com), and Subito.it (www.subito.it). However, 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 Add '--peek' option to 'get-wal' command to discover existing WAL files from the Barman's archive Add 'replication-status' command for monitoring the status of any streaming replication clients connected to the PostgreSQL server. The '--target' option allows users to limit the request to only hot standby servers or WAL streaming clients Add the 'switch-xlog' command to request a switch of a WAL file to the PostgreSQL server. Through the '--force' it issues a 'CHECKPOINT' beforehand Add 'streaming_archiver_name' option, which sets a proper 'application_name' to 'pg_receivexlog' when 'streaming_archiver' is enabled (only for PostgreSQL 9.3 and above) Check for superuser privileges with PostgreSQL's standard connections (#30) Check the WAL archive is never empty Check for 'backup_label' on the master when server is down Improve barman-wal-restore contrib script Bug fixes: Treat the "failed backups" check as non-fatal Rename '-x' option for get-wal as '-z' Add archive_mode=always support for PostgreSQL 9.5 (#32) Properly close PostgreSQL connections when necessary Fix receive-wal for pg_receive_xlog version 9.2 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. [Less]
Posted 2 months ago
PostgreSQL Conference Europe 2016 will be held on November 1-4 in the Radisson Blu Hotel Olümpia, in Tallin, Estonia. It will cover topics for PostgreSQL users, developers and contributors, as well as decision and policy makers. For more information ... [More] about the conference, please see the website at http://2016.pgconf.eu/. 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 24th, 2016. Please submit your proposals by going to http://2016.pgconf.eu/callforpapers/ 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 that 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 are also looking for sponsors. PostgreSQL Conference Europe is a perfect opportunity for companies to reach out to users and developers of PostgreSQL, or to just give back to the community. Our sponsorship program covers a wide range of levels, from entry level to big scale. More informations on http://2016.pgconf.eu/becomesponsor/. We look forward to hearing from you, and seeing you in Tallin in November! [Less]
Posted 2 months ago
2016-05-12 Cumulative Bug Fix Release The PostgreSQL Global Development Group has released an update to all supported versions of our database system, including 9.5.3, 9.4.8, 9.3.13, 9.2.17 and 9.1.22. This release fixes a number of issues reported ... [More] by users over the last two months. Most database administrators should plan to upgrade at the next available downtime, unless they have been affected directly by the fixed issues. Bug Fixes and Improvements This update fixes several problems which caused downtime for users, including: Clearing the OpenSSL error queue before OpenSSL calls, preventing errors in SSL connections, particularly when using the Python, Ruby or PHP OpenSSL wrappers Fixed the "failed to build N-way joins" planner error Fixed incorrect handling of equivalence in multilevel nestloop query plans, which could emit rows which didn't match the WHERE clause. Prevented two memory leaks with using GIN indexes, including a potential index corruption risk. The release also includes many other bug fixes for reported issues, many of which affect all supported versions: Fix corner-case parser failures occurring when operator_precedence_warning is turned on Prevent possible misbehavior of TH, th, and Y,YYY format codes in to_timestamp() Correct dumping of VIEWs and RULEs which use ANY (array) in a subselect Disallow newlines in ALTER SYSTEM parameter values Avoid possible misbehavior after failing to remove a tablespace symlink Fix crash in logical decoding on alignment-picky platforms Avoid repeated requests for feedback from receiver while shutting down walsender Multiple fixes for pg_upgrade Support building with Visual Studio 2015 This update also contains tzdata release 2016d, with updates for Russia, Venezuela, Kirov, and Tomsk. 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. Users who have skipped one or more update releases may need to run additional, post-update steps; please see the release notes for earlier versions for details. Links: Download Release Notes Security Page Abbreviated Keys Issue [Less]
Posted 2 months ago
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 ... [More] , 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 [Less]
Posted 3 months ago
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 ... [More] 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. [Less]
Posted 3 months ago
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 ... [More] 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. [Less]
Posted 3 months ago
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 ... [More] 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/ [Less]
Posted 3 months ago
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 ... [More] 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/ [Less]
Posted 3 months ago
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! ... [More] 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 [Less]
Posted 3 months ago
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 ... [More] 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. [Less]