The PostgreSQL Global Development Group announces today that the first 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, although some details will change before then. Users are encouraged to begin testing their applications against this latest release.

Major Features of 10

The new version contains multiple features that will allow users to both scale out and scale up their PostgreSQL infrastructure:

• Logical Replication: built-in option for replicating specific tables or using replication to upgrade
• Native Table Partitioning: range and list partitioning as native database objects
• Additional Query Parallelism: including index scans, bitmap scans, and merge joins
• Quorum Commit for Synchronous Replication: ensure against loss of multiple nodes

We have also made three improvements to PostgreSQL connections, which we are calling on driver authors to support, and users to test:

• SCRAM Authentication, for more secure password-based access
• Multi-host "failover", connecting to the first available in a list of hosts
• target_session_attrs parameter, so a client can request a read/write host

Additional Features

Many other new features and improvements have been added to PostgreSQL 10, some of which may be as important, or more important, to specific users than the above. Certainly all of them require testing. Among them are:

• Crash-safe and replicable Hash Indexes
• Multi-column Correlation Statistics
• New "monitoring" roles for permission grants
• Latch Wait times in pg_stat_activity
• XMLTABLE query expression
• Restrictive Policies for Row Level Security
• Full Text Search support for JSON and JSONB
• Compression support for pg_receivewal
• ICU collation support
• Push Down Aggregates to foreign servers
• Transition Tables in trigger execution

Further, developers have contributed performance improvements in the SUM() function, character encoding conversion, expression evaluation, grouping sets, and joins against unique columns. Analytics queries against large numbers of rows should be up to 40% faster. Please test if these are faster for you and report back.

See the Release Notes for a complete list of new and changed features.

Test for Bugs and Compatibility

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 10. 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.

Additionally, version 10 contains several changes that are incompatible with prior major releases, particularly renaming "xlog" to "wal" and a change in version numbering. We encourage all users test it against their applications, scripts, and platforms as soon as possible. See the Release Notes and the What's New in 10 page for more details.

Beta Schedule

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

Links

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

Mapt - powered by Packt - is a comprehensive tech library stuffed full of the latest PostgreSQL knowledge. Mapt boasts over 170 hours of PostgreSQL courses, including the latest Packt PostgreSQL eBooks. It’s been designed for developers who need answers fast.

Newly released on Mapt, the PostgreSQL Administration Cookbook, High Performance Cookbook and High Availability Cookbook give you essential answers right at your fingertips. Now PostgreSQL community members can access these titles and more with an exclusive 50% off discount on Mapt Annual subscription.

You can receive a discount off of a whole year of Mapt with the discount code MptPgSQL50

Mapt’s PostgreSQL courses cover everything you need to know whether you’re just starting out with the basics, or looking for advanced tips and tricks to get the most from PostgreSQL. Get practical insight from real PostgreSQL experts with decades of database experience. Mapt authors include Simon Riggs, CTO of PostgreSQL consultancy 2ndQuadrant; Greg Smith, principal consultant for 2ndQuadrant, and Postgre Open speaker Shaun M Thomas.

On top of all that PostgreSQL knowledge, a Mapt subscription nets even more insight. Access to over 4,500 eBook and video courses on data, development, and more. Get career development guidance from Mapt’s Skill Plans. Make your learning stick with assessments, and take advantage of a global author community.

SQL Multi Select 3.2 Basic Edition is now free.

Run multiple scripts on multiple PostgreSQL databases with a single click. A description for how to use SQL Multi Select with other PostgreSQL tools is available here.

Changes in version 3.2:

• various GUI changes to improve Wine compatibility.
• added option to define default scripts for PostgreSQL, MySQL, and Oracle servers
• modified the upgrade process to avoid having to reboot the Linux OS.

System requirements:

• Runs on Windows XP to Windows 10.
• Runs on Wine, tested on Ubuntu and Fedora.
• Supports PostgreSQL 8.3 to 9.6, without the need for any additional database drivers.

For more information about SQL Multi Select for PostgreSQL, please visit http://www.yohz.com/sms_details.htm, or download a free 14-day trial.

About Yohz Software

Yohz Software is a developer of free and commercial database applications for most popular database engines. Visit our site at http://www.yohz.com.

The PostgreSQL Global Development Group has released an update to all supported versions of our database system, including 9.6.3, 9.5.7, 9.4.12, 9.3.17, and 9.2.21. This release fixes three security issues. It also patches a number of other bugs reported over the last three months. Users who use the PGREQUIRESSL environment variable to control connections, and users who rely on security isolation between database users when using foreign servers, should update as soon as possible. Other users should plan to update at the next convenient downtime.

Security Issues

Three security vulnerabilities have been closed by this release:

• CVE-2017-7484: selectivity estimators bypass SELECT privilege checks
• CVE-2017-7485: libpq ignores PGREQUIRESSL environment variable
• CVE-2017-7486: pg_user_mappings view discloses foreign server passwords

The fix for CVE-2017-7486 applies to new databases, see the release notes for the procedure to apply the fix to an existing database.

Any user relying on the PGREQUIRESSL environment variable is encouraged to use the sslmode connection string option, as use of PGREQUIRESSL is deprecated. CVE-2017-7485 does not affect the 9.2 series. 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 the 9.6 series, but many affect all supported versions. There are more than 90 fixes in this release, including:

• Fix to ensure consistent behavior for RLS policies
• Fix ALTER TABLE ... VALIDATE CONSTRAINT to not recurse to child tables when the constraint is marked NO INHERIT
• Fix incorrect support for certain box operators in SP-GiST which could yield incorrect results
• Fixes for handling query cancellation
• Skip tablespace privilege checks when ALTER TABLE ... ALTER COLUMN TYPE rebuilds an existing index
• Fix possibly-invalid initial snapshot during logical decoding
• Fix possible corruption of init forks of unlogged indexes
• Several fixes to postmaster, including checks for when running as a Windows service
• Several planner fixes, among others assorted minor fixes in planning of parallel queries
• Avoid possible crashes in walsender and some index-only scans on GiST index
• Fix cancelling of pg_stop_backup() when attempting to stop a non-exclusive backup
• Updates to ecpg to support COMMIT PREPARED and ROLLBACK PREPARED
• Several fixes for pg_dump/pg_restore, among others to handle privileges for procedural languages and when using --clean option
• Several fixes for contrib modules, such as dblink, pg_trgm and postgres_fdw
• Fixes to MSVC builds, such as using correct daylight-savings rules for POSIX-style time zone names and supporting Tcl 8.6
• Several performance improvements
• Fix cursor_to_xml() to produce valid output with tableforest = false
• Fix roundoff problems in float8_timestamptz() and make_interval()
• Fix pgbench to handle the combination of --connect and --rate options correctly
• Fixes to commandline tools such as pg_upgrade and pg_basebackup
• Several fixes to VACUUM and CLUSTER

Users of replication tools based on logical decoding, as well as users of unlogged indexes, should consult the release notes for potential extra steps during the upgrade.

This update also contains tzdata release 2017b with updates for DST law changes in Chile, Haiti, and Mongolia, plus historical corrections for Ecuador, Kazakhstan, Liberia, and Spain. Switch to numeric abbreviations for numerous time zones in South America, the Pacific and Indian oceans, and some Asian and Middle Eastern countries. The timezone library is synchronized with IANA release tzcode2017b.

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, or two, more updates 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.

After update, users of replication tools based on logical decoding, as well as users of unlogged indexes, should consult the release notes for potential extra steps during the upgrade. See the Release Notes for more details.

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

pg_chameleon is a MySQL to PostgreSQL replica system developed in python 2.7/3.3+.

The release 1.0 comes with the following features

• Copy schema and data from MySQL to a PostgreSQL schema
• MySQL to PostgreSQL replica
• Basic DDL Support (CREATE/DROP/ALTER TABLE, DROP PRIMARY KEY/TRUNCATE)
• Discards of replicated rubbish data
• Replica from multiple MySQL sources
• Basic replica monitoring
• Detach replica from MySQL for easy migration to PostgreSQL

Usage examples

• Analytics
• Migrations
• Data aggregation from multiple MySQL databases

Download and documentation

Pypi package

Github page

Documentation

Oxford, United Kingdom - May 4, 2017

2ndQuadrant is pleased to announce the release of pglogical 2.0 – the next generation in logical replication for PostgreSQL. This version will continue to be supported until EOL for PostgreSQL server versions 9.4, 9.5 and 9.6 and will also work with PostgreSQL 10 due to release in Fall 2017.

What's New

The pglogical 2.0 release brings new features allowing it to be used for even more use-cases. It also includes several bug fixes and behavior improvements, including:

• Row filter - specify SQL expression which should be used on upstream to filter rows for replicated table
• Column filter - specify list of columns that should be replicated, this allows replication of just some columns from a table
• Windows support - pglogical can be now used with PostgreSQL running on Windows as both provider and subscriber (has to be built from the source at the moment)
• Delayed replication - it’s now possible to set delay for how long behind the downstream should be when replicating data
• Postgres-XL support - Postgres-XL can become a pglogical subscriber, which means you can replicated from PostgreSQL to Postgres-XL directly
• New command line tool pglogical_create_subscriber which can convert physical standby (or base backup) into pglogical subscriber
• Performance improvements for applying transactions containing many INSERTs (including transactions that did large import using COPY)
• Improved behavior of TRUNCATE, especially the TRUNCATE triggers
• Users executing DDL in database no longer need USAGE privilege on pglogical schema
• Fixed reporting of false positives on UPDATE conflicts
• Log level for conflicts can now be changed

About pglogical

pglogical is a logical replication system implemented entirely as a PostgreSQL extension. Fully integrated, it requires no triggers or external programs. This alternative to physical replication is a highly efficient method of replicating data using a publish/subscribe model for selective replication.

About 2ndQuadrant

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

pglogical has been developed by 2ndQuadrant. It is open source and fully supported for 2ndQuadrant 24/7 Support customers. We also offer consulting services to help organizations with application development, conflict handler design, cluster design, deployment, feature development and performance analysis.

Yohz Software has just released DB Doc 4.1, the PostgreSQL schema documentation tool, and is available for immediate download.

Changes in this version:

• All reports now display the 20 largest tables (by total size, indexes size, and toast size) and indexes for each schema.
• Added ability to sort table and index lists by any text or numeric property.
• Schema inspector added so you can view the properties of each database object before printing your reports.
• Search function in schema inspector allows you to quickly filter database objects by name and/or comment.
• Fixed consistency of PDF portrait and landscape layouts.
• Improved consistency of Word reports with PDF reports.
• Improved search function dialog in script editor.

DB Doc benefits:

• Create documents in HTML, CHM, PDF, and MS Word formats
• Eliminate tedious and time-consuming manual documentation tasks
• Satisfy audit requirements by keeping complete and timely documentation
• Document a database in 4 simple steps
• View inter-object and inter-database dependencies in your documents
• Document layouts can be fully customizable to suit your requirements
• Keep teams up to date by distributing documentation
• Runs on Windows XP to Windows 10
• Runs in Wine, so you can use DB Doc on your favorite Linux distribution
• Supports PostgreSQL 8.3 to 9.6, without the need for any additional database drivers.

For more details about DB Doc, visit the product page here.

New version of MySQL-to-PostgreSQL has been released with verified support for Heroku, option to convert views and other improvements.

Visit https://www.convert-in.com/mysql-to-postgres.htm for details.

Yohz Software has released PgComment, a FREE Windows tool to easily add/modify comments to your database objects.

PgComment reads your database schema in seconds, and displays the schema in a hierarchical tree view, together with any existing comments. You can then edit the comments directly in the tree view.

With PgComment, you can add comments to tables, columns, indexes, views, domains, sequences, and functions.

Changes are cached locally, and sent to the server in a batch when applied, so you do not have to wait for individual COMMENT ON commands to complete after each change. This allows you to work faster.

Used together with DB Doc, our PostgreSQL schema documentation generator, PgComment allows you to delegate the task of documenting the database objects to the users who are most familiar with the database objects.

For more information on PgComment, please visit http://www.yohz.com/pgc_details.htm, or download the installer.

About Yohz Software

Yohz Software is a developer of database applications for most popular database engines. Visit our web site at http://www.yohz.com to discover what other products we offer.

We are very excited to announce the release of AgensGraph v1.1. It includes both new features and many useful improvements. Since we released AgensGraph v1.0, our team has been hard at work researching and building the best AgensGraph solution for database over the past two months. With improved features and upgraded performance, AgensGraph makes it easier for you to manage, analyze and store your data.

Let’s take a look at the new features and improvements:

? MERGE Clause The MERGE specification is a convenient way to verify specific patterns in a graph. If there is no such pattern, AgensGraph creates the specified pattern automatically. Users can also define the additional behaviors using ON MATCH and ON CREATE optional clauses.

? Variable Length Edge Pattern Queries AgensGraph v1.1 is twice as fast as the previous version (v1.0). Using variable length edge pattern is a concise way to specify degrees of relationships between entities such as finding friends of a friend. This is one of the reasons why users choose graph database over relational database.

? External modules In AgensGraph v1.1, two external modules have been added: Hadoop FDW and HyperLogLog datatype.

Hadoop FDW is a foreign data wrapper which connects HIVE systems to access HDFS files in AgensGraph. Using Hadoop FDW, the data residing in Hadoop can be easily imported into AgensGraph.

AgensGraph v1.1 is a minor release but contains major improvements. There will be more features and modules introduced in the coming months. We will update you accordingly. Please visit AgensGraph v1.1 Release for more detailed information.

AgensGraph Download

See also Github repository

dbMigration .NET v5 is a simple, easy and intuitive multiple database migration and sync tool, With it you can easily migrate schema and data between different databases without complicated procedures.

Supported databases: PostgreSQL, SQL Server, SQL Azure, LocalDB, MySQL, Oracle, IBM DB2, Informix, Vertica, NuoDB, Teradata, Sybase ASE, Firebird, SQLite, SQLCe, VistaDB, Access, dBase, FoxPro, Text, Excel, ODBC, OleDB...etc.

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

Major New features from version 3.8 to 5.0 (2016/10/01~2017/03/10):

• Added support for PostgreSQL <-> VistaDB migration
• Added support for PostgreSQL error detail message
• Added support for PostgreSQL (one/two) dimensional arrays
• Added Multi-Language UI (Options->Language)
• Added Automatically generate foreign keys (PG)
• Ability to add custom delimited file extensions
• Improved Migrating VIEWS/FUNCTIONS/SEQUENCES definitions (PG->PG)
• Improved Data Synchronization
• Improved Automatic Mapping Types (UDT)
• Improved Custom Mapping Types
• Improved Command-Line
• Compiled with Visual Studio 2017
• ...and more

The new version is immediately available for download.

The JDBC group is proud to release a new version, and in keeping with the version renumbering meme we have released version 42.0.0.

Notable changes include:

• Support for PostgreSQL versions below 8.2 was dropped
• java.util.logging is now used for logging: logging documentation
• Ensure executeBatch() can be used with pgbouncer. Previously pgjdbc could use server-prepared statements for batch execution even with prepareThreshold=0 (see issue 742)
• Replication protocol API was added: replication API documentation, PR#550
• Version bumped to 42.0.0 to avoid version clash with PostgreSQL version
• Error position is displayed when SQL has unterminated literals, comments, etc (see issue 688)

Team pgDay Asia is happy to announce that registrations for the conference are now open. For a limited time, we are offering group discounts for 3+ people. Register yourself by clicking: http://2017.pgday.asia/#registration.

Schedule for the 2-day single-track conference has also been published: http://2017.pgday.asia/#schedule

Please note that the 2nd day of the conference is part of FOSSASIA's dedicated PostgreSQL track. Tickets for FOSSASIA can be purchased separately here: http://2017.fossasia.org/tickets/

A special shout out to all our speakers and sponsors. This event is not possible without your support. For anyone wishing to sponsor, please send an email to pgday-asia@googlegroups.com.

pgDay Asia 2017 is scheduled to be held in Singapore on 17th & 18th of March. More details here: http://2017.pgday.asia/. The conference will be held along with FOSSASIA - one of the largest FOSS conference on the planet. pgDay Asia will be PostgreSQL conference series for all PostgreSQL enthusiasts in the Asia Pacific region.

Please join us at PostgreSQL@SCaLE15x!

PostgreSQL@SCaLE is an embedded PostgreSQL conference held as part of SCaLE15x on Thursday and Friday, March 2-3, 2017. We will have 24 one-hour PostgreSQL talks -- two rooms for two days. This is by far the best value for your money of any North American PostgreSQL event!

For the talk schedule, please see:

• Thursday
• Friday

We will also have a PostgreSQL community booth in the exhibition hall all weekend.

SCaLE15x (the 15th annual Southern California Linux Expo), taking place on March 2-5, 2017 at the Pasadena Convention Center, is the largest community-run open-source and free software conference in North America. It is held annually in the Los Angeles area. PostgreSQL@SCaLE is always very popular and well attended. Don't miss out!

There is a nominal registration cost, but we have a 50% discount code: PSQL

Please go register here.

PostgreSQL@SCaLE15x is made possible 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 PostgreSQL@SCaLE15x without the generous support of our sponsors:

2ndQuadrant
Amazon Web Services
Command Prompt
OpenSCG
PostgreSQL Consulting

We hope to see everyone there!

The PostgreSQL@SCaLE15x Committee Joe, Jim, and Gabrielle

The PostgreSQL Global Development Group has released an update to all supported versions of our database system, including 9.6.2, 9.5.6, 9.4.11, 9.3.16, and 9.2.20. This release includes fixes that prevent data corruption issues in index builds and in certain write-ahead-log replay situations, which are detailed below. It also patches over 75 other bugs reported over the last three months.

Users should plan to apply this update at the next scheduled downtime.

Build corruption with CREATE INDEX CONCURRENTLY

There existed a race condition if CREATE INDEX CONCURRENTLY was called on a column that had not been indexed before, then rows that were updated by transactions running at the same time as the CREATE INDEX CONCURRENTLY command could have been indexed incorrectly.

If you suspect this may have happened, the most reliable solution is to rebuild affected indexes after installing this update.

This issue is present in the 9.2, 9.3, 9.4, 9.5, and 9.6 series of PostgreSQL.

Fixes for visibility and write-ahead-log stability

These release contains several fixes to improve the stability of visible data and WAL logging that we wish to highlight here.

Prior to this release, data could be prematurely pruned by a vacuum operation when a special snapshot used for catalog scans was presently available. Specifically, the vacuum operation would not be aware of the oldest xmin for this special snapshot. The error would surface with a message such as:

"cache lookup failed for relation 1255"

This release ensures that vacuum operations will account for the catalog scan snapshots.

Additionally, there are several fixes to improved the stability of write-ahead-logging, including:

* A fix for BRIN index WAL logging where a replay could make a portion of the BRIN index useless and require recomputing
* A fix for an unlogged table where a WAL-log would be created under the "wal_level = minimal" setting, and upon replay after crash, the table would not appear to be properly reset
* A fix in the WAL page header validation when re-reading segments that fixes the error of  "out-of-sequence TLI" that could be reported during recovery

Theses issues are present in the 9.6 series of PostgreSQL releases and may also be present in the 9.2, 9.3, 9.4, and 9.5 series.

Bug Fixes and Improvements

This update also fixes a number of bugs reported in the last few months. Some of these issues affect only the 9.6 series, but many affect all supported versions. There are more than 75 fixes provided in this release, including:

• Several fixes for operating in hot standby mode
• Disallow setting the num_sync field to zero in synchronous_standby_names
• Don't count background worker processes against a user's connection limit
• Fix check for when an extension member object can be dropped
• Fix tracking of initial privileges for extension member objects so that it works correctly with ALTER EXTENSION ... ADD/DROP
• Several vacuum and autovacuum fixes
• Fix CREATE OR REPLACE VIEW to update the view query before attempting to apply the new view options
• Make sure ALTER TABLE preserves index tablespace assignments when rebuilding indexes
• Several fixes to the query planner, including fixes for foreign tables and CTEs
• Several fixes around the full-text search feature to improve accuracy and performance of the search
• Several fixes and performance improvements in several array functions
• Several fixes around the interaction of foreign-key constraints with trigger functions around specific ALTER TABLE operations
• Remove optimizations for date/time data types that returned incorrect data
• Fix incorrect use of view reloptions as regular table reloptions
• Fix incorrect "target lists can have at most N entries" complaint when using ON CONFLICT with wide tables
• Fix spurious "query provides a value for a dropped column" errors during INSERT or UPDATE on a table with a dropped column
• Prevent multicolumn expansion of foo.* in an UPDATE source expression
• Ensure that column typmods are determined accurately for multi-row VALUES constructs
• Several fixes for the psql command-line tool
• Prevent multiple calls of pg_start_backup() and pg_stop_backup() from running concurrently
• Several fixes for pg_dump, pg_restore, and pg_basebackup, including a possible pg_basebackup failure on standby server when including WAL files
• Several fixes for parallel workers and plans for parallel queries including fixing a crash if the number of workers available to a parallel query decreases during a rescan
• Several fixes to PL/pgSQL, PL/Python, and PL/Tcl
• Several fixes for contrib modules
• Allow DOS-style line endings in ~/.pgpass files, even on Unix

Update time zone data files to tzdata release 2016j for DST law changes in northern Cyprus (adding a new zone Asia/Famagusta), Russia (adding a new zone Europe/Saratov), Tonga, and Antarctica/Casey. Historical corrections for Italy, Kazakhstan, Malta, and Palestine. Switch to preferring numeric zone abbreviations for Tonga.

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.

If you believe you have been affected by the aforementioned CREATE INDEX CONCURRENTLY bug, you will have to rebuild the index. Here is an example of how to rebuild an index in a production system without losing the ability to utilize the index:

CREATE INDEX CONCURRENTLY new_index_name ON table_name (column_name);
DROP INDEX CONCURRENTLY old_index_name;
ALTER INDEX new_index_name RENAME TO old_index_name;

Note that using this method means you will briefly have two copies of the same index, so if disk space is an issue you may need to take other approaches.

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

Yohz Software has released SQL Multi Select for PostgreSQL, an invaluable too to add to your toolkit if you manage multiple PostgreSQL servers.

SQL Multi Select runs multiple scripts on multiple servers with a single click.

Say you want to find out the 5 largest tables in each database, on each of your 20 PostgreSQL servers. All you have to do is:

• select the appropriate query group (you can define as many as you want, each containing a different set of servers)
• load the script from disk (you can run as many scripts as you want)
• run the project, and you're done! The results are returned in a single consolidated result set for easy comparison and analysis.

Imagine how SQL Multi Select can help you do your work faster. Need to create a new user account on a set of servers? Just select the appropriate query group, write the script, and run the project. Need to create a new database on a bunch of servers? Prepare the CREATE DATABASE script, select a query group, run the script, and you’re done. The possibilities are endless.

System requirements:

• Runs on Windows XP to Windows 10.
• Supports PostgreSQL 8.3 to 9.6, without the need for any additional database drivers.

For more information about SQL Multi Select for PostgreSQL, please visit http://www.yohz.com/sms_details.htm, or download a free 14-day trial.

About Yohz Software

Yohz Software is a developer of database applications for most popular database engines. Learn more about Yohz Software at http://www.yohz.com.

pgwatch 2: PostgreSQL monitoring made easy

Cybertec Schönig & Schönig GmbH proudly presents pgwatch 2 - the most easy to install monitoring tool for PostgreSQL ever released.

It is based on Grafana and offers out of the box monitoring for PostgreSQL databases. Due to the use of containers, pgwatch 2 can be installed in minutes without having to worry about dependencies and complex installation procedures. It is pre-configured. All it needs is a database connection and you are ready to go.

Fire it up and pgwatch will already collect data and display vital information for you in no time.

pgwatch 2 is Open Source can be used free of charge.

Please share feedback as we will improve pgwatch based on your ideas.

More information can be found on our website

Follow us on twitter @PostgresSupport and share your feedback.

Paris, France - January 24th, 2017

pgBadger is a PostgreSQL performance analyzer, built for speed with fully detailed reports based on your PostgreSQL log files.

pgBadger 9.1 was released today, this is a maintenance release that fix some minor bugs. There is also a new report on error class distribution and some feature enhancements:

• Add report of error class distribution when SQLState is available in the log_line_prefix (see %e placeholder).
• Update SQL Beautifier to pgFormatter v1.6 code.
• Improve error message normalization.
• Add --normalized-only option to generate a text file containing all normalized queries found in a log with count.
• Allow %c (session id) to replace %p (pid) as unique session id.
• Add waiting for lock messages to event reports.
• Add --start-monday option to start calendar weeks in Monday instead of default to Sunday.

Here are the complete list of changes:

• Add report of error class distribution when SQLState is available in the log line prefix. Thanks to jacks33 for the feature request.
• Fix incremental global index on resize. Thanks to clomdd for the report.
• Fix command tag log_line_prefix placeholder %i to allow space character.
• Fix --exclude-line options and removing of obsolete directory when retention is enabled and --noreport is used.
• Fix typo in "vacuum activity table". Thanks to Nicolas Gollet for the patch.
• Fix autovacuum report. Thanks to Nicolas Gollet for the patch.
• Fix author of pgbadger's logo - Damien Cazeils and English in comments. Thanks to Thibaut Madelaine for the patch.
• Add information about pgbouncer log format in the -f option. Thanks to clomdd for the report.
• Add --normalized-only information in documentation.
• Fix broken report of date-time introduced in previous patch.
• Fix duration/query association when log_duration=on and log_statement=all. Thanks to Eric Jensen for the report.
• Fix normalization of messages about advisory lock. Thanks to Thibaut Madelaine for the report.
• Fix report of auto_explain output. Thanks to fch77700 for the report.
• Fix unwanted log format auto detection with log entry from stdin. Thanks to Jesus Adolfo Parra for the report.
• Add left open parentheses to the "stop" chars of regex to look for db client in the prefix to handle the PostgreSQL client string format that includes source port. Thanks to Jon Nelson for the patch.
• Fix some spelling errors. Thanks to Jon Nelson for the patch.
• Allow %c (session id) to replace %p (pid) as unique session id. Thanks to Jerryliuk for the report.
• Allow pgBadger to parse default log_line_prefix that will be probably used in 10.0: '%m [%p] '
• Fix missing first line with interpreter call.
• Fix missing Avg values in CSV report. Thanks to Yosuke Tomita for the report.
• Fix error message in autodetect_format() method.
• Add --start-monday option to start calendar weeks in Monday instead of default to Sunday. Thanks to Joosep Mae for the feature request.
• Fix --histo-average option. Thanks to Yves Martin for the report.
• Remove plural form of --ssh-option in documentation. Thanks to mark-a-s for the report.
• Fix --exclude-time filter and rewrite code to skip unwanted line as well code to update the progress bar. Thanks to Michael Chesterton for the report.
• Fix support to %r placeholder in prefix instead of %h.

Links & Credits

DALIBO would like to thank the developers who submitted patches and the users who reported bugs and feature requests.

pgBadger is an open project. Any contribution to build a better tool is welcome. You just have to send your ideas, features requests or patches using the GitHub tools or directly on our mailing list.

Links :

• Download : https://github.com/dalibo/pgbadger/releases/
• Mailing List : https://groups.google.com/forum/?hl=fr#!forum/pgbadger (pgbadger@googlegroups.com)

About pgBadger :

pgBagder is a new generation log analyzer for PostgreSQL, created by Gilles Darold (also author of ora2pg, the powerful migration tool). pgBadger is a fast and easy tool to analyze your SQL traffic and create HTML5 reports with dynamics graphs. pgBadger is the perfect tool to understand the behavior of your PostgreSQL servers and identify which SQL queries need to be optimized.

Docs, Download & Demo at http://dalibo.github.io/pgbadger/

About DALIBO :

DALIBO is the leading PostgreSQL company in France, providing support, trainings and consulting to its customers since 2005. The company contributes to the PostgreSQL community in various ways, including : code, articles, translations, free conferences and workshops

Check out DALIBO's open source projects at http://dalibo.github.io

Oxford, United Kingdom - January 6, 2017

2ndQuadrant is proud to announce the release of repmgr version 3.3, the popular tool for PostgreSQL failover since 2010.

repmgr 3.3 provides a number of usability improvements for the repmgr command line utility, particularly for the ‘standby clone’ and ‘standby register’ commands. These changes are primarily aimed at making repmgr easier to use when provisioning complex replication clusters.

repmgrd users should take note of the changes to repmgr logging behaviour.

From repmgr 3.3, support for the upcoming PostgreSQL 10 release will be provided as far as possible. PostgreSQL 10 is still under development with significant changes expected to the implementation of replication functionality; anyone wishing to test repmgr with PostgreSQL 10 should build from the repmgr master branch. Links

• Website: https://2ndquadrant.com/en/resources/repmgr/
• Download: http://repmgr.org/download/repmgr-3.3.tar.gz
• Release Notes: http://repmgr.org/release-notes-3.3.html
• Installation Instructions: https://2ndquadrant.com/en/resources/repmgr/installation-instructions/
• Documentation: https://github.com/2ndQuadrant/repmgr/blob/master/README.md
• Professional Support: https://2ndquadrant.com/en/support/support-postgresql/ About

repmgr is an open source package that helps DBAs and System Administrators manage a cluster of PostgreSQL databases. By taking 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.

repmgr is distributed under GPL v3 and maintained by 2ndQuadrant.

2ndQuadrant announces the release of Barman version 2.1, a Backup and Recovery Manager for PostgreSQL.

This minor release fixes a few bugs. It also introduces the --archive option to the switch-xlog command, in order to help users during the installation process of a new server.

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
• Client utilities for Barman
• pgespresso extension

Release notes

• Add --archive and --archive-timeout options to switch-xlog command
• Preliminary support for PostgreSQL 10 (#73)
• Minor additions:
  • Add last archived WAL info to 'diagnose' output
  • Add start time and execution time to the output of 'delete' command
• Minor bug fixes:
  • Return failure for 'get-wal' command on inactive server
  • Make 'streaming_archiver_names' and 'streaming_backup_name' options global (#57)
  • Fix rsync failures due to files truncated during transfer (#64)
  • Correctly handle compressed history files (#66)
  • Avoid de-referencing symlinks in 'pg_tblspc' when preparing recovery (#55)
  • Fix comparison of last archiving failure (#40, #58)
  • Avoid failing recovery if postgresql.conf is not writable (#68)
  • Fix output of 'replication-status' command (#56)
  • Exclude files from backups like pg_basebackup (#65, #72)
  • Exclude directories from other Postgres versions while copying tablespaces (#74)

Download

• Release Notes
• Sources
• RPMs for RHEL/CentOS 5 (dependencies)
• RPMs for RHEL/CentOS 6 (dependencies)
• RPMs for RHEL/CentOS 7 (dependencies)
• PyPI
• pgespresso on PostgreSQL Extension framework (PGXN)
• pgespresso RPM/Debian packages
• barman-cli 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 to reduce risk and help DBAs during the recovery phase.

Barman is distributed under GNU GPL 3 and maintained by 2ndQuadrant.