Activity Not Available
I Use This!

News

Analyzed about 1 month ago. based on code collected about 1 month ago.
Posted 20 days ago
Oxford, United Kingdom - August 11, 2016 Bi-Directional Replication for PostgreSQL (Postgres-BDR, or BDR) is the first open source multi-master replication system for PostgreSQL to reach full production status, developed by 2ndQuadrant and assisted ... [More] by a keen user community. BDR is specifically designed for use in geographically distributed clusters, using highly efficient asynchronous logical replication, supporting anything from 2-48 nodes in a distributed database. WHAT'S NEW? Significant improvements related to stability and bug fixes have been made in this release. The most important factors of this release are: Smoother handling of schema changes (DDL) statements allowing increased operational stability and reduced maintenance. Various bug fixes for operational issues demonstrating high level of maturity Performance tuning, especially of global sequence handling Removal of the now deprecated UDR Extensive documentation improvements based upon user feedback For a more comprehensive list of release notes, please click here: http://bdr-project.org/docs/stable/release-1.0.0.html SUPPORT & RELEASE SCHEDULE Postgres-BDR 9.4 1.0 will be supported until December 2019, when PostgreSQL 9.4 goes EOL. BDR continues to be developed and BDR9.6 will be released within 6 months. The BDR project has already delivered the majority of its code into PostgreSQL core, though it will likely be about 2-3 more years before this functionality is available in PostgreSQL core. IS Postgres-BDR RIGHT FOR YOU? BDR is well suited for databases where: Data is distributed globally Majority of data is written to from only one node at a time (For example, the US node mostly writes changes to US customers, each branch office writes mostly to branch-office-specific data, and so on.) There is a need for SELECTs over complete data set (lookups and consolidation) There are OLTP workloads with many smaller transactions Transactions mostly touching non overlapping sets of data There is partition and latency tolerance However, this is not a comprehensive list and use cases for BDR can vary based on database type and functionality. In addition, BDR aids business continuity by providing increased availability during network faults. Applications can be closer to the data and more responsive for users, allowing for a much more satisfying end-user experience. PROFESSIONAL SUPPORT FOR BDR BDR is developed and supported by 2ndQuadrant. 2ndQuadrant provides professional support for BDR, as well as consultation and training. With our deep knowledge of distributed databases, we will ensure that you are able to evaluate your use case and applications and determine the most suitable product or solution. BDR is also available in 2ndQuadrant Cloud, initially on AWS. For more information, please visit the homepage: https://2ndquadrant.com/en/resources/bdr/. [Less]
Posted 20 days ago
The PostgreSQL Global Development Group announces today that the fourth 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] , including fixes to many of the issues found in the first and second betas. Users are encouraged to continue testing their applications against 9.6 beta 4. Changes Since Beta 3 9.6 Beta 4 includes the security fixes in the 2016-08-11 Security Update, as well as the general bug fixes offered for stable versions. Additionally, it contains fixes for the following beta issues reported since the last beta: Change minimum max_worker_processes from 1 to 0 Make array_to_tsvector() sort and de-duplicate the given strings Fix ts_delete(tsvector, text[]) to cope with duplicate array entries Fix hard to hit race condition in heapam's tuple locking code Prevent "snapshot too old" from trying to return pruned TOAST tuples Make INSERT-from-multiple-VALUES-rows handle targetlist indirection Do not let PostmasterContext survive into background workers Add missing casts in information schema Fix assorted problems in recovery tests Block interrupts during HandleParallelMessages() Remove unused arguments from pg_replication_origin_xact_reset function Correctly handle owned sequences with extensions Many fixes for tsqueue.c Eliminate a few more user-visible "cache lookup failed" errors Teach parser to transform "x IS [NOT] DISTINCT FROM NULL" to a NullTest Allow functions that return sets of tuples to return simple NULLs Repair damage done by citext--1.1--1.2.sql Correctly set up aggregate FILTER expression in partial-aggregation plans This beta also includes many documentation updates and improvements. Due to changes in system catalogs, a pg_upgrade or pg_dump and restore will be required for users migrating databases from earlier betas. Note that some known issues remain unfixed. Before reporting a bug in the beta, please check the Open Items page. Beta Schedule This is the fourth 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 20 days ago
The PostgreSQL Global Development Group has released an update to all supported versions of our database system, including 9.5.4, 9.4.9, 9.3.14, 9.2.18 and 9.1.23. This release fixes two security issues. It also patches a number of other bugs ... [More] reported over the last three months. Users who rely on security isolation between database users should update as soon as possible. Other users should plan to update at the next convenient downtime. Security Issues Two security holes have been closed by this release: CVE-2016-5423: certain nested CASE expressions can cause the server to crash. CVE-2016-5424: database and role names with embedded special characters can allow code injection during administrative operations like pg_dumpall. The fix for the second issue also adds an option, -reuse-previous, to psql's \connect command. pg_dumpall will also refuse to handle database and role names containing line breaks after the update. For more information on these issues and how they affect backwards-compatibility, see the Release Notes. 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.5, but many affect all supported versions: Fix misbehaviors of IS NULL/IS NOT NULL with composite values Fix three areas where INSERT ... ON CONFLICT failed to work properly with other SQL features. Make INET and CIDR data types properly reject bad IPv6 values Prevent crash in "point ## lseg" operator for NaN input Avoid possible crash in pg_get_expr() Fix several one-byte buffer over-reads in to_number() Don't needlessly plan query if WITH NO DATA is specified Avoid crash-unsafe state in expensive heap_update() paths Fix hint bit update during WAL replay of row locking operations Avoid unnecessary "could not serialize access" with FOR KEY SHARE Avoid crash in postgres -C when the specified variable is a null string Fix two issues with logical decoding and subtransactions Ensure that backends see up-to-date statistics for shared catalogs Prevent possible failure when vacuuming multixact IDs in an upgraded database When a manual ANALYZE specifies columns, don't reset changes_since_analyze Fix ANALYZE's overestimation of n_distinct for columns with nulls Fix bug in b-tree mark/restore processing Fix building of large (bigger than shared_buffers) hash indexes Prevent infinite loop in GiST index build with NaN values Fix possible crash during a nearest-neighbor indexscan Fix "PANIC: failed to add BRIN tuple" error Prevent possible crash during background worker shutdown Many fixes for issues in parallel pg_dump and pg_restore Make pg_basebackup accept -Z 0 as no compression Make regression tests safe for Danish and Welsh locales The libpq client library has also been updated to support future two-part PostgreSQL version numbers. This update also contains tzdata release 2016f, with updates for Kemerovo, Novosibirsk, Azerbaijan, Belarus, and Morocco. EOL Warning for Version 9.1 PostgreSQL version 9.1 will be End-of-Life in September 2016. The project expects to only release one more update for that version. We urge users to start planning an upgrade to a later version of PostgreSQL as soon as possible. See our Versioning Policy for more information. Updating All PostgreSQL update releases are cumulative. As with other minor releases, users are not required to dump and reload their database or use pg_upgrade in order to apply this update release; you may simply shut down PostgreSQL and update its binaries. 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 Versioning Policy [Less]
Posted about 1 month ago
The PostgreSQL Global Development Group announces today that the third 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] , including fixes to many of the issues found in the first and second betas. Users are encouraged to continue testing their applications against 9.6 beta 3. Changes Since Beta 2 Our users and contributors tested the first two betas, and found and reported many bugs and usability issues. This beta release fixes many of those issues. If you reported an issue, please test this beta to ensure that it's completely fixed. This included many more fixes to parallel query: adding support for TABLESAMPLE correcting cost data in Gather nodes check parallel-safety of all appended relations fix planner issues with initPlans fix several issues with client_encoding clean up EXPLAIN output for parallel queries multiple changes to parallel aggregation internals Among the other issues addressed were: add conninfo field to pg_stat_wal_receiver clear all-frozen visibilitymap status when locking tuples correctly dump database and tablespace ACLs avoid invalidating all foreign-join cached plans when user mappings change fix nested NOT operation cleanup in tsquery allow IMPORT FOREIGN SCHEMA within pl/pgsql print a given subplan only once in EXPLAIN change the GetForeignUpperPaths API fix several issues in postgres_fdw added many additional regression tests many documentation updates and clarifications multiple translation updates for the docs Due to changes in system catalogs, a pg_upgrade or dump and restore will be required for users migrating databases from earlier betas. This includes a version update to the pg_control tool, making it incompatible with PostgreSQL 9.4 and earlier. This beta also includes patches to many issues shared with earlier versions, which will be updated in an upcoming minor release. Note that some known issues remain unfixed. Before reporting a bug in the beta, please check the Open Items page. Beta Schedule This is the third beta release of version 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 about 1 month ago
Crunchy Certified PostgreSQL Receives Level 2 + Certification, Meeting Common Criteria’s Rigid Standards and Organizations’ Security Needs Charleston, SC — July 19, 2016 — Crunchy Data, a leading provider of trusted open source PostgreSQL and ... [More] PostgreSQL technology, support and training, today announced that Crunchy Certified PostgreSQL, the company’s commercially available distribution of PostgreSQL 9.5, has been awarded Common Criteria Evaluation Assurance Level (EAL) 2+ certification, an international standard for computer security certification. It is the first commercially available 100% open source relational database management system to receive Common Criteria certification. For more information please see the full press release here. [Less]
Posted about 1 month ago
Notable changes include : Many improvements to insert into .. values(?,?) -> insert .. values(?,?), (?,?)... rewriter. Give it a try by using reWriteBatchedInserts=true connection property. 2-3x improvements for insert batch can be expected ... [More] Full test suite passes against PostgreSQL 9.6, and OpenJDK 9 Performance optimization for timestamps (~TimeZone.getDefault optimization) Allow build-from-source on GNU/Linux without maven repositories, and add Fedora Copr test to the regression suite The full changelog can be found here [Less]
Posted about 1 month ago
PostgreSQL Conference Europe 2016 in Tallin, Estonia, on November 1-4 is now accepting registrations for conference attendance at http://2016.pgconf.eu/registration/. The Early Bird special price will be available until September 14th, and is ... [More] limited to 75 tickets which is a great reason to get your registration in early! There are also six training sessions available for registration - two full day and four half day sessions - for the Tuesday before the main event. These are all limited space sessions, so make sure you register early if you want to attend! And don't forget - the call for papers is still open! If you have already submitted a talk, or are planning to submit one, we suggest you wait to register until you have received a confirmation if the talk was accepted or not. The early bird rate will be available long enough for you to register after you have received this notification - and if your talk is accepted, attendance is of course free! We are accepting proposals for talks in English. Each session will last 45 minutes, and may be on any topic related to PostgreSQL. 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. 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. The full call for papers is available on the website As usual, if you have any questions, don't hesitate to contact us at contact@pgconf.eu. [Less]
Posted about 2 months ago
I am happy to announce the new major release of Database .NET 18.9. 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 ... [More] with a consistent interface. Free, All-In-One, Portable, Single executable file and Multi-language. Major New features from version 18.1 to 18.9: PostgreSQL 9.6 compatibility Added Support for multi-dimensional arrays (PG) Added Support for bigserial datatype (PG) Added Support for Reporting Errors and Messages (PG) Added Support for LISTEN (listen for a notification) (PG) Added Support for browsing delimited text files Added Automatic reconnection Ability to Cancel executing command Ability to Copy Selected Results to Clipboard Ability to Calculate Selected Cells Ability to Export Results to PSV/SSV (Pipe and Semicolon delimited) (.psv;.ssv) Improved SQL History Improved Query Builder Improved Binding Procedure and Function parameters Improved Transaction Mode Improved Find In Grid 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 For more information please visit http://fishcodelib.com/Database.htm. [Less]
Posted about 2 months ago
2ndQuadrant is delighted to announce the release of repmgr 3.1.4 - the most popular tool for PostgreSQL failover management. First introduced in 2010, repmgr helps DBAs and System Administrators manage a cluster of PostgreSQL databases. By taking ... [More] advantage of the Hot Standby capability introduced in PostgreSQL 9, repmgr greatly simplifies the process of setting up and managing databases with high availability and scalability requirements. Several improvements and bug fixes have been implemented, particularly better path handling and node shutdown detection during switchover operations. To view the release notes, please click here. [Less]
Posted about 2 months ago
New versions of Postgres Migration Tookit has been released with improved support for schemas, default values, "pure" time and many other improvements. Visit http://www.convert-in.com/pgskit.htm for details.