Skip to content

Software Development News: .NET, Java, PHP, Ruby, Agile, Databases, SOA, JavaScript, Open Source

Methods & Tools

Subscribe to Methods & Tools
if you are not afraid to read more than one page to be a smarter software developer, software tester or project manager!

PostgreSQL News
Syndicate content
PostgreSQL news
Updated: 2 hours 24 min ago

Advisory on May 22 Update Release

Tue, 05/26/2015 - 01:00

On May 22, 2015, the PostgreSQL Global Development Group released an update to all supported versions of PostgreSQL, including versions 9.4.2, 9.3.7, 9.2.11, 9.1.16, and 9.0.20. This update has a bug in fsync logic which will cause some users' PostgreSQL servers to refuse to restart after a crash, or after a restore from binary backup. Please read our FAQ on this issue before applying the update to your systems.

The PostgreSQL Project regrets the error. Another PostgreSQL update, with this issue corrected, will be released soon.

Categories: Database, Open Source

PostgreSQL 9.4.2, 9.3.7, 9.2.11, 9.1.16, and 9.0.20 released!

Fri, 05/22/2015 - 01:00

The PostgreSQL Global Development Group has released an update with multiple functionality and security fixes to all supported versions of the PostgreSQL database system, which includes minor versions 9.4.2, 9.3.7, 9.2.11, 9.1.16, and 9.0.20. The update contains a critical fix for a potential data corruption issue in PostgreSQL 9.3 and 9.4; users of those versions should update their servers at the next possible opportunity.

Please see the FAQ about a potential issue with this update for some users before applying it.

Data Corruption Fix

For users of PostgreSQL versions 9.3 or 9.4, this release fixes a problem where the database will fail to protect against "multixact wraparound", resulting in data corruption or loss. Users with a high transaction rate (1 million or more per hour) in a database with many foreign keys are especially vulnerable. We strongly urge all users of 9.4 and 9.3 to update their installations in the next few days.

Users of versions 9.2 and earlier are not affected by this issue.

Security Fixes

This update fixes three security vulnerabilities reported in PostgreSQL over the past few months. None of these issues are seen as particularly urgent. However, users should examine them in case their installations are vulnerable:

  • CVE-2015-3165 Double "free" after authentication timeout.
  • CVE-2015-3166 Unanticipated errors from the standard library.
  • CVE-2015-3167 pgcrypto has multiple error messages for decryption with an incorrect key.

Additionally, we are recommending that all users who use Kerberos, GSSAPI, or SSPI authentication set include_realm to 1 in pg_hba.conf, which will become the default in future versions.

More information about these issues, as well as older patched issues, is available on the PostgreSQL Security Page.

Other Fixes and Improvements

A new, non-default version of the citext extension fixes its previously undocumented regexp_matches() functions to align with the ordinary text version of those functions. The fixed version has a different return type than the old version, so users of CIText should test their applications before updating the function by running "ALTER EXTENSION citext UPDATE".

In addition to the above, more than 50 reported issues have been fixed in this cumulative update release. Most of the issues named affect all supported versions. These fixes include:

  • Render infinite dates and timestamps as infinity when converting to json
  • Fix json/jsonb's populate_record() and to_record()
  • Fix incorrect checking of deferred exclusion constraints
  • Improve planning of star-schema-style queries
  • Fix three issues with planning joins
  • Ensure correct locking with security barrier views
  • Fix deadlock at startup when max_prepared_transactions is too small
  • Recursively fsync() the data directory after a crash
  • Fix autovacuum launcher's possible failure to shut down
  • Cope with unexpected signals in LockBufferForCleanup()
  • Fix crash when doing COPY IN to a table with check constraints
  • Avoid waiting for synchronous replication of read-only transactions
  • Fix two issues with hash indexes
  • Prevent memory leaks in GIN index vacuum
  • Fix two issues with background workers
  • Several fixes to Logical Decoding replication
  • Fix several minor issues with pg_dump and pg_upgrade

This release includes an update to tzdata release 2015d, with updates to Egypt, Mongolia, and Palestine, plus historical changes in Canada and Chile.

9.0 EOL Soon

Version 9.0 will become End-Of-Life in September 2015. This means that this update is likely to be the next-to-last update for that version. Users of PostgreSQL 9.0 should start planning to upgrade to a more current version before then. See our versioning policy for more information about EOL dates.

Updating

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 multiple update releases may need to perform additional post-update steps; see the Release Notes for details.

Links:

Categories: Database, Open Source

pgBadger 7.0 released !

Tue, 05/12/2015 - 01:00

Paris, France - Mai 11th, 2014

DALIBO is proud to announce the release of pgBadger 7.0.

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

New reports and support for explain.depesz.com

This major release adds more useful reports and features. One of the longest feature request have been also implemented, support to auto_explain extension. EXPLAIN plan will be added together with top slowest queries when available in log files. Thanks to the kind authorization of depesz, a link to automatically open directly the explain plan on http://explain.depesz.com/ is also available.

List of other new reports in this release:

  • Events (panic, fatal, error and warning) distribution per 5 minutes.
  • Per application details (total duration and times executed) for each query reported in Top Queries. The details are visible from a button called "App(s) involved".
  • Cumulated queries durations per user.

Three new reports to help identifying queries cancelled on secondaries clusters:

  • Number of cancelled queries (graph)
  • Queries generating the most cancellation (N)
  • Queries most cancelled.

For the complete list of changes, please checkout the release note on https://github.com/dalibo/pgbadger/blob/master/ChangeLog

Links & Credits

DALIBO would like to thank the developers who submitted patches and the users who reported bugs and feature requests, especially Mael Rimbault, Thomas Reiss, Korriliam, rlowe and Antti Koivisto.

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 :

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

Categories: Database, Open Source

Call for Papers - PostgreSQL Conference Europe 2015

Tue, 05/12/2015 - 01:00

PostgreSQL Conference Europe 2015 will be held on October 27-30 in the Vienna Marriott Hotel, in Vienna, Austria. It will cover topics for PostgreSQL users, developers and contributors, as well as decision and policy makers. For more information about the conference, please see the website.

We are now accepting proposals for talks in English or German. If you are submitting a talk in German, please write a short summary of the abstract in English in the "submission notes" field.

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, 2015.

Please submit your proposals by going to http://2015.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 look forward to hearing from you, and seeing you in Vienna in October!

Categories: Database, Open Source

Barman 1.4.1 released

Tue, 05/05/2015 - 01:00

05 May 2015: 2ndQuadrant is proud to announce the release of version 1.4.1 of Barman, Backup and Recovery Manager for PostgreSQL.

This minor release fixes a few outstanding bugs and does not introduce any new features.

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

Links

Release notes

  • Fix for WAL archival stop working if first backup is EMPTY (Closes: #64)
  • Fix exception during error handling in Barman recovery (Closes: #65)
  • After a backup, limit cron activity to WAL archiving only (Closes: #62)
  • Improved robustness and error reporting of the "backup delete" command (Closes: #63)
  • Fix computation of WAL production ratio as reported in the "show-backup" command
  • Improved management of xlogb file, which is now correctly fsynced when updated. Also, the "rebuild-xlogdb" command now operates on a temporary new file, which overwrites the main one when finished.
  • Add unit tests for dateutil module compatibility
  • Modified Barman version following PEP 440 rules and added support of tests in Python 3.4

Download

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.

Categories: Database, Open Source

Call for Papers, PostgreSQL Session #7, September, 24th

Mon, 04/20/2015 - 01:00

After six 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), and to PostgreSQL performance (March 2013), we'd like to announce that the 7th PostgreSQL Session will be held on September 24th, 2015, in Paris, France.

This year, another place, but always the same format! This day of lectures will be dedicated especially to the next version of PostgreSQL, but not exclusively!

For more information, see http://www.postgresql-sessions.org/7/about

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:

  • What's New in PostgreSQL
  • Use cases
  • Migration to PostgreSQL
  • Performance Tuning
  • Backup and Restore
  • High-Availibity
  • Data Warehouse / Big Data
  • 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 June 15, 2015.

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 Paris in September!

About the PostgreSQL Sessions:

The PostgreSQL sessions are designed to be a time to discover and meet the PostgreSQL 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.

Categories: Database, Open Source

PostgreSQL Maestro 15.4 released

Thu, 04/09/2015 - 01:00

SQL Maestro Group announces the release of PostgreSQL Maestro 15.4, a powerful Windows GUI solution for PostgreSQL database server administration and database development.

The new version is immediately available for download.

Top 10 new features:
  1. Tablespace Editor now displays objects belonging to the tablespace.
  2. SQL Formatter now supports WITH queries, queries with the RETURNING clause and LATERAL JOINs.
  3. Adding new values to existing ENUM types.
  4. ALTER SYSTEM statement on changing the value of a server variable.
  5. Executing custom SQL scripts in all database connections established by the software.
  6. Support for a number of new encryption algorithms in data grids.
  7. Colored tabs and more informative tab hints.
  8. Updated Data Export and Data Import tools.
  9. Improved Data Input Form.
  10. Some performance and usability improvements.

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

Categories: Database, Open Source

PostgreSQL Data Sync 15.3 released

Thu, 03/26/2015 - 01:00

SQL Maestro Group announces the release of PostgreSQL Data Sync 15.3, a powerful and easy-to-use tool for PostgreSQL database contents comparison and synchronization.

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

Top 5 new features:
  1. An ability to select or disable certain synchronization operations (Insert, Update, and Delete) has been implemented. The corresponding command line switches have been added as well.
  2. Now it is possible to specify SQL scripts to be executed before and/or after synchronizing data of each table.
  3. Synchronization script file name and log file name are now stored in the project file. These settings can be overwritten with the appropriate command line options.
  4. The first page of the wizard has been redesigned in order to provide more comfortable access to recently opened projects and display the latest company news.
  5. The progress windows are redesigned in the modern style and become more informative.

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

Categories: Database, Open Source

PostgresOpen 2015 in Dallas - Call For Papers!

Tue, 03/17/2015 - 01:00

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

If you are working with PostgreSQL, please visit and submit a talk!

We're looking for presentations 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!

We look forward to bringing the best PostgreSQL presentations and tutorials from speakers around the world to the first multi-day PostgreSQL conference in Texas!

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

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

Early Bird registration for PostgresOpen 2015 will start on May 4th.

We look forward to seeing everyone in Dallas!

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

Categories: Database, Open Source

Registration for PGConf US 2015 Closing Soon. Very Soon.

Tue, 03/17/2015 - 01:00

If you've waited until the last minute to come to PGConf US 2015, that minute has arrived.

In only a week, registration will be closed for PGConf US 2015. PGConf US 2015 is taking place from March 25 - 27 and the New York Marriott Downtown in New York City, and is hosted by the United States PostgreSQL Association.

If you have not already, we invite you to review our schedule at http://www.pgconf.us/2015/schedule/. This year we have 4 tracks of talks, including a track focusing just on PostGIS and its applications.

We could not produce PGConf US 2015 without the generous support of our sponsors, including our platinum sponsors EnterpriseDB, 2ndQuadrant, and Citus Data, and our gold sponsors Amazon Web Services and Airfacts.

We hope to see you in a week!

Categories: Database, Open Source

Database .NET 14.7 released

Fri, 03/13/2015 - 01:00

I am happy to announce the new major release of Database .NET 14.7, an innovative, powerful and intuitive multiple database management tool, With it you can Browse objects, Design tables, Edit rows, Export data and Run queries with a consistent interface.

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

Major New features from version 14.1 to 14.7:

  • Updated to Npgsql.dll 2.2.5
  • Added My Favorites
  • Added Specifying dynamic variables
  • Added Specifying specific printers
  • Added Pin to Start Menu and Pin to Taskbar
  • Added Default placeholders
  • Added Hiding and Unhiding columns
  • Added Moving Row Up and Down for Cell Viewer and Form Viewer
  • And more...
The new version is immediately available for download.
Categories: Database, Open Source

Meet the PostgresDAC v3.0.0

Wed, 03/04/2015 - 01:00
We've released our new major version of PostgresDAC component suite. It’s been a long way started almost two years ago. The goals were complicated, and not all of them were accomplished. However, in general we may proudly say without a doubt that this release is a significant milestone. Dump and restore functionality

TPSQLDump and TPSQLRestore components is a pair that is one of a kind on the whole market. There are no more such facilities not only in the Delphi or C Builder world, but for any other IDE's or toolchains. That is why our first goal was to keep this classes up to date. A huge amount of work was done and a year ago the brand new v3 TPSQLDump and TPSQLRestore components were published as part of v2.11.0 release.

TPSQLDump and TPSQLRestore are fully compatible with native pg_dump and pg_restore utilities. Each and every native feature is supported out of the box:

  • output formats (binary, text, directory, gzipped),
  • parallel dumping and restoring,
  • comprehensive selection, filtering and reordering of archived items,
  • SQL-92 specific output options, etc.
Asynchronous Fetch-On-Demand mode

The default TPSQLQuery's mode is suitable for submitting commands and getting result sets in normal, synchronous applications. However, there are few drawbacks, that may be of importance to developers:

  • TPSQLQuery.Open waits for the command to be completed. The application might have other work to do (such as maintaining a user interface), in which case it won’t be a good decision to block while waiting for a response.
  • Since the execution of the client application is suspended while it waits for the result, it is hard for the application to decide that it would like to try to cancel the ongoing command.
  • TPSQLQuery in default mode always collects a command's entire result, buffering it in a single place. While this behavior simplifies some internal logic, it can be impractical for results containing many rows.

To avoid such limitations developers now can use the brand new Fetch-On-Demand mode, which is turned on by dsoFetchOnDemand option in the TPSQLQuery.Options set. There are limitations of course:

  • To get advantages of the Fetch-On-Demand mode one should use read-only TPSQLQuery objects. This restriction will be removed with time probably.
  • Each read-only TPSQLQuery component must have its separate TPSQLDatabase component since Fetch-On-Demand command flow will block a connection until getting the last row of the result set.
Support for built-in range and geometric field types

Previously these specific types were mapped to TStringField class. Now PostgresDAC provides new TField descendants for this:

  • TPSQLRangeField
  • TPSQLPointField
  • TPSQLCircleField
  • TPSQLBoxField
  • TPSQLLSegField

All of them will be created automatically if needed, or may be added manually in design time.

TPSQLRangeField encapsulates all built-in PostgreSQL range types: int4range, int8range, numrange, tsrange, tstzrange and daterange. Information about range value is stored in the TPSQLRange record by storing values for each bound using TPSQLRangeBound record. Depending on the underlying table field type developer may access bound values using appropriate methods AsInteger, AsFloat, etc.

Enhanced Manual

We've finished the new help system. It's rewritten it from scratch. Support for such formats provided:

  • chm,
  • pdf.
  • epub (in progress).
Full changelog:
  • [!] Fetch-On-Demand mode introduced for readonly TPSQLQuery objects
  • [!] Support for geometric types added
  • [!] TPSQLRangeField added
  • [!] Support for pre-8.0 PostgreSQL servers is discontinued
  • [!] v9.4.0 client libraries added
  • [!] v9.4.0 dump & restore libraries (pg_dump.dll, pg_restore.dll) added
  • [*] Components TPSQLUser and TBDE2PSQLDAC marked as deprecated and will be removed shortly
  • [*] EPSQLDatabaseError is raised if TPSQLDatabase is used in non-exclusive mode for TPSQLQuery with dsoFetchOnDemand
  • [*] TPSQLDatabase.CancelBackend checks for connection now to prevent AV
  • [-] "AV may occur if SQL parameter name consists from incorrect characters chain" bug fixed
  • [-] "EPSQLDatabaseError detail error properties are empty after error in TPSQLDirectQuery.Open" bug fixed
Download

You're welcome to download the PostgresDAC v3.0.0 right now at: http://microolap.com/products/connectivity/postgresdac/download/ or login to your private area on our site at http://microolap.com/my/downloads/

Feedback

Please don't hesitate to ask any questions or report bugs with our Support Ticketing system available at http://www.microolap.com/support/

Categories: Database, Open Source

Fujitsu Develops Column-Oriented Data-Processing Engine that accelerates analytic processing more than fifty-fold on a single server with PostgreSQL open-source database

Tue, 03/03/2015 - 01:00

Fujitsu Laboratories Ltd. today announced that it has developed a column-oriented data-storage and processing engine that enables fast analysis of large volumes of data in a database system.

In recent years, column-oriented databases have emerged as a system that allows for better speed when reading and analyzing large volumes of data, as a counterpart to existing row-oriented databases, which are suited to handling data updates. But problems have been either that the changes to row-oriented data cannot be automatically reflected in column-oriented data, or that the size of the column-oriented data is constrained by installed memory.

Fujitsu has developed an engine that, running on a PostgreSQL open-source database, without being dependent on memory capacity, instantly updates column-oriented data in response to changes in row-oriented data, and processes column-oriented data quickly. The engine quickly analyzes indexes(1), which are provided by most database systems, and can be used by developers without special consideration to whether the storage method is row-oriented or column-oriented. With a parallel-processing engine especially suited for processing column-oriented data, analyses run on a single CPU core are conducted 4 times faster than before, and one server equipped with 15 CPU cores can run analyses at least 50 times faster.

For more information please visit http://www.fujitsu.com/global/about/resources/news/press-releases/2015/0226-01.html

Categories: Database, Open Source

PoWA 2: Finding the Missing Index !

Mon, 03/02/2015 - 01:00

Paris, March 2 2015

DALIBO is proud to present the second release of PoWA, the PostgreSQL Workload Analyzer.

Complete rewrite of the User Interface

The first major change is the new graphic design : we've rebuilt the web interface from scratch and placed it on a separate module called powa-web. It is now easier to move the PoWA interface out of the database server.

The new interface is based on the previous version and it adds many improvements, including:

  • More graphs
  • New types of graph : Bar / Pie Charts
  • New configuration view
  • New index suggestion widget
  • New physical resource consumption graphs
  • Better Global Query Chart
  • Breadcrumbs
  • Python 2.6, 2.7 and 3.4 compatibility
  • Better browser compatibility

 

Screenshot:

http://powa.readthedocs.org/en/latest/stats_extensions/pg_stat_statements.html#where-is-it-used-in-powa-web

Advanced Filesystem Stats

Second, the core-engine of PoWA is now a separate module too: it's called powa-archivist and we've extended it to archive any kind of internal stats. The main source of stats remains the pg_stat_statements extension but we've integrated 2 other extensions: pg_qualstats and pg_stat_kcache.

With pg_stat_kcache, PoWA is now able to gather statistics about the physical disk access and the CPU consumption of each PostgreSQL backend. This allows the DBA to get a glimpse of the OS-level cache hit ratio.

Screenshot:

http://powa.readthedocs.org/en/latest/stats_extensions/pg_stat_kcache.html#where-is-it-used-in-powa-web

Missing Index Finder + Advanced WHERE Clause Analyzer

Third major improvement, with pg_qualstats PoWA is now collecting metrics about the operations in the WHERE clause of each query. With this data, you can know what are the most common values in your SQL statements and evaluate their "selectivity". And for columns with a very high selectivity and no index, PoWA will suggest index creation to speed up you queries.

Screenshot:

http://powa.readthedocs.org/en/latest/stats_extensions/pg_qualstats.html#where-is-it-used-in-powa-web

Disruptive changes

It was a hard choice but if we want to implement ground-breaking features like the Missing Index Finder, we need to use the latest capacities of PostgreSQL and thus we decided to drop the compatibility with PostgreSQL 9.3.

Of course, we will continue to maintain PoWA v1.2 and you can continue to use it on your PostgreSQL 9.3 servers. In a nutshell, If you already use PoWA here's what you need to know:

  • If you're running PostgreSQL 9.4, we recommend that you switch to PoWA 2.0
  • If you're running PostgreSQL 9.3, you can either keep PoWA 1.2 or upgrade your PostgreSQL instance and switch to PoWA 2.0

 

Here's a detailed explanation on why we are Moving Fast and Breaking Things

Credits & Licence

DALIBO would like to thank all the developers who contributed to this release: Rodolphe Quiedeville, Hyunjun Kim, Grégoire Pineau, Ahmed Bessifi, exordium-frozen, Christopher Liu, menardorama and especially Ronan Dunklau and Julien Rouhaud for the hard work on the GUI.

POWA is an open project available under the PostgreSQL License. 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 to powa@dalibo.com

Links :

For PoWA 2.0:

 

For the new stats extensions:

 

For the complete list of changes, please checkout the release note on http://powa.readthedocs.org/en/latest/releases/v2.0.html

About POWA :

PoWA is a PostgreSQL Workload Analyzer that gathers performance stats and provides real-time charts and graph to help monitor and tune your PostgreSQL servers. It is similar to Oracle AWR or SQL Server MDW.

Code & Demo at http://dalibo.github.io/powa/

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

Categories: Database, Open Source