PostgreSQL News

Syndicate content
PostgreSQL news
Updated: 15 weeks 5 days ago

DBConvert / DBSync for PostgreSQL and Oracle released.

17 December, 2013 - 03:00

DBConvert/DBSync for PostgreSQL & Oracle has been released. Applications support conversion and synchronization between PostgreSQL and Oracle in both directions. It takes about 5-7 minutes to transfer 1 Million of records.

Trigger-based database replication method and simultaneous bidirectional synchronization help you to manage your data easy and efficiently. You can sync your databases automatically or manually.

FInd more information at:

DBConvert for Oracle & PostgreSQL

DBSync for Oracle & PostgreSQL

Database .NET 10 released!

15 December, 2013 - 03:00

Database .NET 10 is a major release with many major improvements. (It was first released in June 2006)

New features and improvements from version 8.5~10.0:
  • (Main) Support for PostgreSQL 8.x/9.x.
  • (Main) Updated to Npgsql.dll
  • (Main) New Graphical User Interface
  • (Main) Allowed NOSUPERUSER permission for PostgreSQL
  • (Main) Support for MATERIALIZED VIEW
  • (Main) Added SQL History
  • (Main) Added Quick Filter
  • (Main) Added Security Manager
  • (Main) Added PrimaryKey Selector
  • (Main) Added Custom backcolor for current connection
  • (Main) Added Dock Window
  • (Main) Improved Command-line
  • (Main) Improved Generate Scripts
  • (Main) Improved Table Designer
  • (Main) Improved Data Editor and Form Editor
  • (Main) Improved Data Import and Export
  • (Main) Improved Data Visualization
  • (Main) Improved Search Objects
  • (Main) Improved SQL Profiler
  • (Main) Improved Code Snippets Manager
  • (SQL Editor) Added Query Builder
  • (SQL Editor) Added Splitter mode and Tabbed mode
  • (SQL Editor) Added Recentily Used Files
  • (SQL Editor) Added Highlight Search Terms
  • (SQL Editor) Added Code Folding
  • (SQL Editor) Added Additional Commands
  • (SQL Editor) Added Timer for Automatic Execution
  • (SQL Editor) Added Execute current statemen (Ctrl+Enter)
  • (SQL Editor) Added AutoComplete + Code Snippets
  • (SQL Editor) Improved AutoComplete and IntelliSense
  • (SQL Editor) New Quick Find and Replace
  • Free, Portable, Easy to Use and Multlanguage.

The new version is immediately available for download.

Windows Workflow Foundation is now supported in dotConnect for PostgreSQL

12 December, 2013 - 03:00

Devart Team is glad to announce the release of the new version of dotConnect for PostgreSQL - enhanced database connectivity solutions built on ADO.NET architecture that support Entity Framework and LinqConnect ORM solutions. New versions of dotConnect data providers support Windows Workflow Foundation.

From now on, developers can use Workflow Tracking and persist state information about workflow instances in PostgreSQL databases.

To get more information about new ADO.NET data providers features visit the following page:

dotConnect for PostgreSQL 7.2 [ Download New features ]

About Devart

Devart is a recognized vendor of database connectivity solutions for Microsoft .NET and Embarcadero Delphi development platforms as well as database development and management software. Company's solutions support such databases as Microsoft SQL Server, Oracle, MySQL, PostgreSQL, InterBase, Firebird, and SQLite. Along with database oriented software Devart offers productivity tools for Visual Studio which help developers to be empowered, stay focused, and deliver their best all the time.

For additional information about Devart, visit

PostgreSQL Maintenance Releases: 9.3.2, 9.2.6, 9.1.11, 9.0.15, and 8.4.19

5 December, 2013 - 03:00

The PostgreSQL Global Development Group has released a critical update to all supported versions of the PostgreSQL database system, which includes minor versions 9.3.2, 9.2.6, 9.1.11, 9.0.15, and 8.4.19. This update fixes three serious data-loss bugs affecting replication and database maintenance. All users are urged to update their installations at the earliest opportunity.

The replication issue affects some users of PostgreSQL binary replication, and can cause minor data loss between the master and the standby. While not all users are affected, it is difficult to predict when the bug will occur, so we urge all users of replication and continuous backup (PITR) to update immediately. Additionally, users who had replication running under PostgreSQL minor versions 9.3.0, 9.3.1, 9.2.5, 9.1.10, or 9.0.14 should plan to take a fresh base backup of each standby after update, in order to ensure no prior data corruption already exists. More information about this issue is on its wiki page.

This release also fixes two timing issues with VACUUM, which can cause old, overwritten or deleted rows to re-appear at a later date under some circumstances. Users with very high transaction rates, particularly those who experience "transaction ID wraparound" every few weeks or less, are the most at risk for this issue. Those users should set vacuum_freeze_table_age to 0, and run a database-wide VACUUM after the update. The second of the two VACUUM issues affects only 9.3, making it expecially important for 9.3 users to update.

Additional fixes included in this release, some of which only affect version 9.3, include:

  • Prevent "lock already held" error.
  • Resolve race conditions in timeout management, which could cause server lockup.
  • Fix minor bugs with HOT updates and the Visibility Map.
  • Prevent pg_multixact storage growth on standbys.
  • Fix bug in GIN indexes which caused transient query failures.
  • Remove issue which caused SP-GiST index creation to hang
  • Fix assorted bugs in Materialized Views.
  • Restore ability to use duplicate table aliases in complex queries.
  • Fix two bugs in subquery optimization.
  • Allow pg_receivexlog to resume streaming when more than 4GB of logs are generated.
  • Prevent planner crash on whole-row references.
  • Prevent premature deletion of temporary files.
  • Patch multiple minor memory leaks.
  • Suppress display of dropped columns for CHECK and NOT NULL constraint violations.
  • Allow default and named arguments for window functions.
  • Return a valid JSON value when converting an empty HStore string.
  • Fix GMT timezone offset.
  • Report out-of-disk-space error correctly during pg_upgrade.
  • Time zone updates for several time zones.

Additional changes and details of some of the above issues can be found in the Release Notes.

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: * Download * Release Notes

Replication Bug Warning

22 November, 2013 - 03:00

The PostgreSQL Project has recently discovered an issue which can cause minor data loss for some users of streaming replication on very recent releases. Details on this issue are explained on the November 2013 Replication Data Loss Issue page, as well as steps to protect yourself until the next update release is available.

We apologize for any disruption caused by this issue. We expect to have an update available which fixes this issue in less than 2 weeks.

Intelligent Converters released PostgreSQL-to-MSSQL and MSSQL-to-PostgreSQL converters

18 November, 2013 - 03:00

Intelligent Converters has extended their product line with new tools to migrate between Microsoft SQL and SQL Azure databases and PostgreSQL.

For more information, please visit the product pages list below:

MSSQL-to-PostgreSQL Converter

PostgreSQL-to-MSSQL Converter

pgBadger 4: Brand New Design, Time Period Exclusion and more !

31 October, 2013 - 03:00

Paris, France - October 31th, 2013

DALIBO is proud to announce the release of pgBadger 4, a PostgreSQL performance analyzer, built for speed with fully detailed reports based on your Postgres log files.

This major version comes with a bunch of new features including a complete overhaul for the HTML reports, some new statistics, compatiblity with PostgreSQL 9.3 and Time Period Exclusion...

Better Reports / Improved user experience

With a full rewrite of its graphic design, pgBadger has now turned the HTML reports into a more intuitive user experience and professional look.

Every statistic report now include a key value section that shows you immediately some of the relevant informations. Pie charts have also been separated from their data tables using two tabs, one for the chart and the other one for the data.

Tables reporting hourly statistic have been moved to a multiple tabs report following the data. This is used with General (queries, connections, sessions), Checkpoints (buffer, files, warnings), Temporary file and Vacuums activities.

PostgreSQL 9.3 compatibility and new stats

Recent PostgreSQL versions add additional information about checkpoint, the number of synced files, the longest sync and the average of sync time per file. pgBadger collects and shows these informations in the Checkpoint Activity report.

There's also some new reports:

  • Prepared queries ratio (execute vs prepare)
  • Prepared over normal queries
  • Queries (select, insert, update, delete) per user/host/application
  • Pie charts for tables with the more tuples and pages removed during vacuum. The vacuum report will now highlight the costly table during a vacuum or analyze of a database.

The errors are now highlighted by a different color following the level. A LOG level will be green, HINT will be yellow, WARNING orange, ERROR red and FATAL dark red.

Some changes in the binary format are not backward compatible and option --client have been remove as it was replaced by --dbclient for a long time now.

Time Period Exclusion

If you are running a pg_dump or some batch process with very slow queries your report analyze will be annoyed by those queries taking too much place in the report. Before that release it was a pain to exclude those queries from the report. Now you can use the --exclude-time command line option to exclude all traces matching the given time regexp from the report. For example, let's say you have a pg_dump at 13:00 each day during half an hour, you can use pgbadger as follow:

pgbadger --exclude-time "2013-09-.* 13:.*" postgresql.log

If your are also running a pg_dump at night, let's say 22:00, you can write it as follow:

pgbadger --exclude-time '2013-09-\d+ 13:[0-3]' --exclude-time '2013-09-\d+ 22:[0-3]' postgresql.log

or more shortly:

pgbadger --exclude-time '2013-09-\d+ (13|22):[0-3]' postgresql.log

Exclude time always require the iso notation yyyy-mm-dd hh:mm:ss, even if log format is syslog. This is the same for all time related options. Take care that this option has a high cost on the parser performances.

Links & Credits

DALIBO would like to thank the developers who submitted patches and the users who reported bugs and feature requests, especially Keith Fiske, Marco Baringe, Herve Werner, Den Untevskiy and Mael Rimbault. The new HTML report was designed by Art Is Code.

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.

  • Download :
  • Mailing List :

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


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

DbWrench Database Design v3.0.1 Released

17 October, 2013 - 03:00
DbWrench Database Design v3.0.1 Released

Version 3.0.1 is a major milestone in DbWrench development and the first release of version 3.

This release focused on significant enhancements to the diagram editor. These enhancements include:

- Diagram lines are now movable. - A new right angle linking algorithm to reduce line collisions and overlap with glyphs. - A new diagram glyph color fill algorithm to make diagram glyphs more readable. - Improved memory management to further improve performance.

A free trial download of this latest version is available at

Screen shots can be viewed here.

More About DbWrench

DbWrench is designed to increase the productivity of database developers by making creating and modifying databases much easier.

It's features include:

- Graphic entity relation diagram (ERD) designer - Forward engineer database designs with automatic SQL DDL script generation - Reverse engineer and visualize existing databases - A built in syntax highlighting SQL query editor - Runs on Windows, Mac OSX and Linux all in a single license

E-Maj 1.1.0 released

11 October, 2013 - 03:00

A new E-Maj version, named 1.1.0, is now available from or github.

E-Maj is an Open Source extension for PostgreSQL. It contains functions to log updates performed on one or several sets of tables, and cancel ("rollback") these updates if needed, resetting a tables set to a predefined stable state. A dedicated plugin for phpPgAdmin also brings a nice GUI to these features.

The main improvement of this 1.1.0 version resides in the E-Maj rollback mechanism. It has been largely improved in order to get better performance and to allow administrator to monitor in progress operations. Functions that generate sql scripts from logged updates have been also enhanced.

The documentation and the CHANGES file supplied with the extension give all the details about the E-Maj features and usage and the latest improvements.

E-Maj 1.1.0 supports postgres version 8.3 to 9.3.

All E-Maj users working with previous versions are invited to upgrade (supplied migration scripts may help in performing this operation).

Have fun with E-Maj !

PostgreSQL 2013-10-10 Update Release

10 October, 2013 - 03:00

The PostgreSQL Global Development Group has released a bug-fix update to all current versions of the PostgreSQL database system, including versions 9.3.1, 9.2.5, 9.1.10, 9.0.14, and 8.4.18. This release fixes many minor issues reported by our community over the last six months. All users should update their PostgreSQL installations at the next regular maintenance window.

In this release are fixes for the recently-released version 9.3, including:

  • Update hstore extension with JSON functionality
  • Prevent memory leak when creating range indexes
  • Fix libpq SSL deadlock bug

In addition to the above, there are a few dozen minor bug fixes for older versions. These patches were already included in 9.3.0 when released. Among them are:

  • Guarantee transmission of all WAL files before replica failover
  • Prevent downcasing of non-ASCII identifiers
  • Fix several minor memory leaks
  • Correct overcommit behavior when using more than 24GB of work memory
  • Improve planner cost estimates for choosing generic plans
  • Fix estimates of NULL rows in boolean columns
  • Make UNION ALL and inheritance query plans recheck parameterized paths
  • Correct pg_dump bugs for foreign tables, views, and extensions
  • Prevent a parallel pg_restore failure on certain indexes
  • Make REINDEX revalidate constraints
  • Prevent two deadlock issues in SP-GIST and REINDEX CONCURRENTLY
  • Prevent GiST index lookup crash
  • Fix several regular expression failures
  • Allow ALTER DEFAULT PRIVILEGES to work on all schemas
  • Loosen restrictions on keywords
  • Allow various spellings of infinity
  • Expand ability to compare rows to records and arrays
  • Prevent psql client crash on bad PSQLRC file
  • Add spinlock support for ARM64

Note that users of the hstore extension on version 9.3 must take an additional, post upgrade step of running "ALTER EXTENSION hstore UPDATE" in each database after update.

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: * Download * Release Notes