PostreSQL.org

The PostgreSQL Global Development Group announces that the first beta release of PostgreSQL 12 is now available for download. This release contains previews of all features that will be available in the final release of PostgreSQL 12, though some details of the release could change before then.

In the spirit of the open source PostgreSQL community, we strongly encourage you to test the new features of PostgreSQL 12 in your database systems to help us eliminate any bugs or other issues that may exist. While we do not advise you to run PostgreSQL 12 Beta 1 in your production environments, we encourage you to find ways to run your typical application workloads against this beta release.

Your testing and feedback will help the community ensure that the PostgreSQL 12 release upholds our standards of providing a stable, reliable release of the world's most advanced open source relational database.

PostgreSQL 12 Features Highlights Indexing Performance, Functionality, and Management

PostgreSQL 12 improves the overall performance of the standard B-tree indexes with improvements to the space management of these indexes as well. These improvements also provide a reduction of index size for B-tree indexes that are frequently modified, in addition to a performance gain.

Additionally, PostgreSQL 12 adds the ability to rebuild indexes concurrently, which lets you perform a REINDEX operation without blocking any writes to the index. This feature should help with lengthy index rebuilds that could cause downtime when managing a PostgreSQL database in a production environment.

PostgreSQL 12 extends the abilities of several of the specialized indexing mechanisms. The ability to create covering indexes, i.e. the INCLUDE clause that was introduced in PostgreSQL 11, has now been added to GiST indexes. SP-GiST indexes now support the ability to perform K-nearest neighbor (K-NN) queries for data types that support the distance (<->) operation.

The amount of write-ahead log (WAL) overhead generated when creating a GiST, GIN, or SP-GiST index is also significantly reduced in PostgreSQL 12, which provides several benefits to the disk utilization of a PostgreSQL cluster and features such as continuous archiving and streaming replication.

Inlined WITH queries (Common table expressions)

Common table expressions (aka WITH queries) can now be automatically inlined in a query if they a) are not recursive, b) do not have any side-effects and c) are only referenced once in a later part of a query. This removes an "optimization fence" that has existed since the introduction of the WITH clause in PostgreSQL 8.4

If need be, you can force a WITH query to materialize using the MATERIALIZED clause, e.g.

WITH c AS MATERIALIZED ( SELECT * FROM a WHERE a.x % 4 = 0 ) SELECT * FROM c JOIN d ON d.y = a.x;

Partitioning

PostgreSQL 12 improves on the performance when processing tables with thousands of partitions for operations that only need to use a small number of partitions.

PostgreSQL 12 also provides improvements to the performance of both INSERT and COPY into a partitioned table. ATTACH PARTITION can now be performed without blocking concurrent queries on the partitioned table. Additionally, the ability to use foreign keys to reference partitioned tables is now permitted in PostgreSQL 12.

JSON path queries per SQL/JSON specification

PostgreSQL 12 now allows execution of JSON path queries per the SQL/JSON specification in the SQL:2016 standard. Similar to XPath expressions for XML, JSON path expressions let you evaluate a variety of arithmetic expressions and functions in addition to comparing values within JSON documents.

A subset of these expressions can be accelerated with GIN indexes, allowing the execution of highly performant lookups across sets of JSON data.

Collations

PostgreSQL 12 now supports case-insensitive and accent-insensitive comparisons for ICU provided collations, also known as "nondeterministic collations". When used, these collations can provide convenience for comparisons and sorts, but can also lead to a performance penalty as a collation may need to make additional checks on a string.

Most-common Value Extended Statistics

CREATE STATISTICS, introduced in PostgreSQL 10 to help collect more complex statistics over multiple columns to improve query planning, now supports most-common value statistics. This leads to improved query plans for distributions that are non-uniform.

Generated Columns

PostgreSQL 12 allows the creation of generated columns that compute their values with an expression using the contents of other columns. This feature provides stored generated columns, which are computed on inserts and updates and are saved on disk. Virtual generated columns, which are computed only when a column is read as part of a query, are not implemented yet.

Pluggable Table Storage Interface

PostgreSQL 12 introduces the pluggable table storage interface that allows for the creation and use of different methods for table storage. New access methods can be added to a PostgreSQL cluster using the CREATE ACCESS METHOD command and subsequently added to tables with the new USING clause on CREATE TABLE.

A table storage interface can be defined by creating a new table access method.

In PostgreSQL 12, the storage interface that is used by default is the heap access method, which is currently is the only built-in method.

Page Checksums

The pg_verify_checkums command has been renamed to pg_checksums and now supports the ability to enable and disable page checksums across a PostgreSQL cluster that is offline. Previously, page checksums could only be enabled during the initialization of a cluster with initdb.

Authentication & Connection Security

GSSAPI now supports client-side and server-side encryption and can be specified in the pg_hba.conf file using the hostgssenc and hostnogssenc record types. PostgreSQL 12 also allows for discovery of LDAP servers based on DNS SRV records if PostgreSQL was compiled with OpenLDAP.

Noted Behavior Changes

There are several changes introduced in PostgreSQL 12 that can affect the behavior as well as management of your ongoing operations. A few of these are noted below; for information about other changes, please review the "Migrating to Version 12" section of the release notes.

1. The recovery.conf configuration file is now merged into the main postgresql.conf file. PostgreSQL will not start if it detects that recovery.conf is present. To put PostgreSQL into a non-primary mode, you can use the recovery.signal and the standby.signal files.

You can read more about archive recovery here:

https://www.postgresql.org/docs/devel/runtime-config-wal.html#RUNTIME-CONFIG-WAL-ARCHIVE-RECOVERY

1. Just-in-Time (JIT) compilation is now enabled by default.

2. OIDs can no longer be added to user created tables using the WITH OIDs clause. Operations on tables that have columns that were created using WITH OIDS (i.e. columns named "OID") will need to be adjusted.

Running a SELECT * command on a system table will now also output the OID for the rows in the system table as well, instead of the old behavior which required the OID column to be specified explicitly.

Additional Features

Many other new features and improvements have been added to PostgreSQL 12, some of which may be as or more important to specific users than what is mentioned above. Please see the Release Notes for a complete list of new and changed features.

Testing for Bugs & Compatibility

The stability of each PostgreSQL release greatly depends on you, the community, to test the upcoming version with your workloads and testing tools in order to find bugs and regressions before the general availability of PostgreSQL 12. 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 please test in the near future. The quality of user testing helps determine when we can make a final release.

A list of open issues is publicly available in the PostgreSQL wiki. You can report bugs using this form on the PostgreSQL website:

https://www.postgresql.org/account/submitbug/

Beta Schedule

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

Links

• Download
• Beta Testing Information
• PostgreSQL 12 Beta Release Notes
• PostgreSQL 12 Open Issues
• Submit a Bug

Oxford, United Kingdom - May 17, 2019

2ndQuadrant today announced the release of Barman version 2.8, introducing support for incremental backup in geo-redundancy. It also includes various performance enhancements and bug fixes.

Barman 2.8 deprecates support for PostgreSQL 9.3 and older versions, and declares official support for Python 3 - deprecating Python 2.

Barman (Backup and Recovery Manager) is an open source administration tool for managing backup and disaster recovery of PostgreSQL servers. It allows you to perform remote backups of multiple servers in business-critical environments and helps DBAs during the recovery phase.

This release includes performance enhancements and other changes listed below:

• Add support for reuse_backup in geo-redundancy for incremental backup copy in passive nodes
• Improve performance of rsync based copy by using strptime instead of the more generic dateutil.parser
• Add --test option to barman-wal-archive and barman-wal-restore to verify the connection with the Barman server
• Complain if backup_ options is not explicitly set, as the future default value will change from exclusive_backup to concurrent _backup when PostgreSQL 9.5 will be declared EOL by the PGDG
• Display additional settings in the show-server and diagnose commands: archive_ timeout, data_ checksums, hot_ standby, max_ wal _ senders, max _ replication_ slots and wal_ compression.
• Merge the barman-cli project in Barman

We strongly recommend upgrading to Barman v2.8 at the earliest opportunity available.

Upgrade Information Users of rsync backup method on a primary server should set backup_ options to either concurrent_ backup (recommended for PostgreSQL 9.6 or higher) or exclusive_ backup (current default) before upgrading to Barman 2.8.

A complete list of changes and bug fixes is available here.

Download and installation instructions are available here.

Source files are available for download here.

Barman is developed and maintained by 2ndQuadrant and distributed under GPL v3.

For more information, please send an email to info@2ndQuadrant.com

What is Pgpool-II?

Pgpool-II is a tool to add useful features to PostgreSQL, including:

• connection pooling
• load balancing
• automatic fail over and more.

Minor releases

Pgpool Global Development Group is pleased to announce the availability of following versions of Pgpool-II:

• 4.0.5
• 3.7.10
• 3.6.17
• 3.5.21
• 3.4.24

Release notes for versions prior 3.6 are no longer included in the source code.

Please take a look at release notes.

You can download the source code and RPMs.

Devart launched the next version of dbForge Studio for PostgreSQL v.2.1 with a new query optimization feature, Greenplum DB connectivity, and a bunch of other notable improvements.

Devart, a recognized vendor of professional database management software for developers and DBAs, released dbForge Studio for PostgreSQL v2.1. The updated version has a new connectivity option, a brand new feature for optimizing queries, and a redesigned Execute Large Script Wizard, as well as Database Explorer and Code Completion improvements.

The new edition includes the following enhancements:

Greenplum DB Support — dbForge Studio for PostgreSQL broadened its database connectivity. From now on, Greenplum, an open-source massively parallel DBMS, is officially in a list of supported databases, which greatly expands the app’s capabilities.

New Query Profiler — the new Query Profiler functionality helps to locate bottlenecks and visually optimize slow SQL queries. The profiling results are neatly displayed in several tabs, providing the following profiling stats and data: plan tree and diagram of query execution, list of the top operations taking place on the server, and an execution plan in XML format.

Database Explorer Improvements — after the update, Database Explorer can display such database objects and nodes as domains, rules & triggers for views, and indexes for materialized views.

Code Completion Improvements — SQL coding became even more convenient with these useful code completion features:

• Prompting the names of existing materialized views in the REFRESH MATERIALIZED VIEW;
• Context prompting of database objects in the SELECT queries’ FROM list;
• Syntax support for the VACUUM statement;
• Prompting keywords for Functions;
• Prompting keywords in SELECT queries.

Redesign of Execute Large Script Wizard — the wizard automatically selects the connection and database specified in the connection settings by default. The database list can also be refreshed.

dbForge Studio for PostgreSQL is a GUI tool for database development and management. This IDE for PostgreSQL allows users to create, develop and execute queries, edit and adjust the code to specific requirements in a convenient and user-friendly interface. For more information about dbForge Studio for PostgreSQL, please visit https://blog.devart.com/whats-new-dbforge-studio-pgsql-21.html

About Devart

Devart is one of the leading developers of database tools and administration software, ALM solutions, data providers for various database servers, data integration and backup solutions. The company also implements Web and Mobile development projects. For additional information about Devart, visit https://www.devart.com/

The PostgreSQL Global Development Group has released an update to all supported versions of our database system, including 11.3, 10.8, 9.6.13, 9.5.17, and 9.4.22. This release fixes two security issues in the PostgreSQL server, a security issue found in two of the PostgreSQL Windows installers, and over 60 bugs reported over the last three months.

Users who installed PostgreSQL using the Windows installers from EnterpriseDB and BigSQL respectively should upgrade as soon as possible. Similarly, users who are running any version of PostgreSQL 9.5, 9.6, 10, and 11 should also plan to upgrade as soon as possible.

All other users should plan to apply this update at the next scheduled downtime.

Security Issues

Four security vulnerabilities have been closed by this release:

• CVE-2019-10127: BigSQL Windows installer does not clear permissive ACL entries
• CVE-2019-10128: EnterpriseDB Windows installer does not clear permissive ACL entries

Due to both the EnterpriseDB and BigSQL Windows installers not locking down the permissions of the PostgreSQL binary installation directory and the data directory, an unprivileged Windows user account and an unprivileged PostgreSQL account could cause the PostgreSQL service account to execute arbitrary code.

This vulnerability is present in all supported versions of PostgreSQL for these installers, and possibly exists in older versions. Both sets of installers have fixed the permissions for these directories for both new and existing installations. If you have installed PostgreSQL on Windows using other methods, we advise that you check that your PostgreSQL binary directories are writable only to trusted users and that your data directories are only accessible to trusted users.

The PostgreSQL project thanks Conner Jones for reporting this problem.

• CVE-2019-10129: Memory disclosure in partition routing

Prior to this release, a user running PostgreSQL 11 can read arbitrary bytes of server memory by executing a purpose-crafted INSERT statement to a partitioned table.

• CVE-2019-10130: Selectivity estimators bypass row security policies

PostgreSQL maintains statistics for tables by sampling data available in columns; this data is consulted during the query planning process. Prior to this release, a user able to execute SQL queries with permissions to read a given column could craft a leaky operator that could read whatever data had been sampled from that column. If this happened to include values from rows that the user is forbidden to see by a row security policy, the user could effectively bypass the policy. This is fixed by only allowing a non-leakproof operator to use this data if there are no relevant row security policies for the table.

This issue is present in PostgreSQL 9.5, 9.6, 10, and 11. The PostgreSQL project thanks Dean Rasheed for reporting this problem.

Bug Fixes and Improvements

This update also fixes over 60 bugs that were reported in the last several months. Some of these issues affect only version 11, but many affect all supported versions.

Some of these fixes include:

• Several catalog corruption fixes, including one related to running ALTER TABLE on a partitioned table
• Several fixes for partitioning
• Avoid server crash when an error occurs while trying to persist a cursor query across a transaction commit
• Avoid O(N^2) performance issue when rolling back a transaction that created many tables
• Fix possible “could not access status of transaction” failures in txid_status()
• Fix updatable views to handle explicit DEFAULT items in INSERT .. VALUES statements where there are multiple VALUES rows
• Fix CREATE VIEW to allow zero-column views
• Add missing support for the CREATE TABLE IF NOT EXISTS .. AS EXECUTE .. statement
• Ensure that sub-SELECTs appearing in row-level-security policy expressions are executed with the correct user's permissions
• Accept XML documents as valid values of type xml when xmloption is set to content, as required by SQL:2006 and later
• Fix incompatibility of GIN-index WAL records that were introduced in 11.2, 10.7, 9.6.12, 9.5.16, and 9.4.21 that affected replica servers running these versions reading in changes to GIN indexes from primary servers of older versions
• Several memory leak fixes as well as fixes to management of dynamic shared memory
• Relax panics on fsync and sync_file_range failures for certain cases where a failure indicated "operation not supported"
• Several fixes to the query planner, several of which should lead to planning improvements
• Fix race condition in which a hot-standby postmaster could fail to shut down after receiving a smart-shutdown request
• Several fixes for SCRAM authentication
• Fix handling of lc_time settings that imply an encoding different from the database's encoding
• Create the current_logfiles file with the same permissions as other files in the server's data directory
• Several ecpg fixes
• Make pg_verify_checksums verify that the data directory it's pointed at is of the right PostgreSQL version
• Several fixes for contrib/postgres_fdw, including one for remote partitions where an UPDATE could lead to incorrect results or a crash
• Several Windows fixes

This update also contains tzdata release 2019a for DST law changes in Palestine and Metlakatla, plus historical corrections for Israel. Etc/UCT is now a backward-compatibility link to Etc/UTC, instead of being a separate zone that generates the abbreviation UCT, which nowadays is typically a typo. PostgreSQL will still accept UCT as an input zone abbreviation, but it won't output it.

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

PostgreSQL 9.4 will stop receiving fixes on February 13, 2020. Please see our versioning policy for more information.

Links

• Download
• Release Notes
• Security Page
• Versioning Policy
• Follow @postgresql on Twitter

The PostgreSQL Project is excited to announce that we have been accepted by Google to participate in the first Google Season of Docs (GSoD)!

This program's goal is to provide a framework for experienced technical writers and open source projects to work together towards the common goal of improving an open source project's documentation.

Between now and May 28th 2019, interested technical writers should discuss their project ideas with the project, after which proposals will be made through the GSoD system.

For more information about GSoD, please visit the GSoD website:

https://developers.google.com/season-of-docs/

For more information about working with the PostgreSQL project as part of GSoD, please visit our GSoD website:

https://wiki.postgresql.org/wiki/GSoD

PostgreSQL Conference Europe 2019 takes place in Milan, Italy, on October 15-18. Our Call for Papers is now open.

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 July 15th. Selected speakers will be notified before August 10th, 2019.

Please submit your proposals by going to 2019.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. The members of the committee are listed on the website linked above.

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 so 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 or contact us separately before the submission deadline.

And finally, our Call for Sponsorship is also open. Take your chance to present your services or products to the PostgreSQL community - or see it as a give back opportunity. All sponsorship levels also include one or more free entrance tickets, depending on the level. Please head to 2019.pgconf.eu/becomesponsor/ for more details.

Please note that the hotel room situation in Milan is tense, we advise you to book your room as early as possible. We are working with hotels around the venue to provide more options.

As usual, if you have any questions, don't hesitate to contact us at contact@pgconf.eu.

We look forward to seeing you in Milan in October!

The PostgreSQL Code of Conduct Committee has delivered their 2018 Annual Report summarizing the types of complaints received and actions taken since the Code of Conduct took effect in 2018 through the end of the year. All complaints and actions are anonymized to protect the identities of all parties involved.

You can view a copy of the report here: https://www.postgresql.org/about/policies/coc/reports/2018/

There is widespread mention in the media of a security vulnerability in PostgreSQL, registered as CVE-2019-9193. The PostgreSQL Security Team would like to emphasize that this is not a security vulnerability. We believe the CVE entry was filed in error. We have contacted the reporter to investigate the issue.

The COPY .. PROGRAM feature explicitly states that it can only be executed by database users that have been granted superuser privileges or the default role pg_execute_server_program. By design, this feature allows one who is granted superuser or pg_execute_server_program to perform actions as the operating system user the PostgreSQL server runs under (normally "postgres"). The default roles pg_read_server_files and pg_write_server_files that are mentioned in the CVE do not grant permission for a database user to use COPY .. PROGRAM.

By design, there exists no security boundary between a database superuser and the operating system user the server runs under. As such, by design the PostgreSQL server is not allowed to run as an operating system superuser (e.g. "root"). The features for COPY .. PROGRAM added in PostgreSQL 9.3 did not change any of the above, but added a new command within the same security boundaries that already existed.

We encourage all users of PostgreSQL to follow the best practice that is to never grant superuser access to remote or otherwise untrusted users. This is a standard security operating procedure that is followed in system administration and extends to database administration as well.

If you have more questions about this, we invite you to reach out to members of the community through one of our support resources:

https://www.postgresql.org/support/

Links

• COPY Documentation
• CVE-2019-9193
• Security Page
• Support
• Follow @postgresql on Twitter

New milestone PostgresDAC release is out! Now with PostgreSQL 11 and RAD Studio 10.3 Rio support

PostgresDAC is a direct access component suite for RAD Studio (Delphi and C++Builder)/FreePascal/Lazarus and PostgreSQL, EnterpriseDB, Amazon RDS, PostgresPro and Heroku Postgres.

Full changelog:

• [!] New installer introduced
• [!] RAD Studio 10.3 Tokyo (Delphi and C++ Builder) support introduced
• [+] TPSQQLQuery.BeforeExecSQL event added
• [-] "NUMERIC caused AV in Delphi 6" bug fixed

Download

You're welcome to download the PostgresDAC v3.5 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/

Oxford, United Kingdom - April 2, 2019

2ndQuadrant today announced the release of repmgr 4.3 This major release includes several important enhancements, making usage of repmgr more flexible and powerful.

repmgr is the most popular tool for PostgreSQL replication and failover management, which enhances and complements the built-in replication capabilities in PostgreSQL. This makes repmgr easy to set up to manage standby servers, check replication status, and perform administrative tasks such as switchover operations.The repmgrd daemon provides automatic failover capability to maximize database uptime, and can easily be integrated with other tools such as PgBouncer for high application availability.

repmgr 4.3 presents the following usability enhancements:

• repmgr standby follow. Option --upstream-node-id can now be used to specify another standby to follow.
• repmgr standby follow. Verifies that it is possible to follow another node.
• repmgr node rejoin. Verifies that it is possible to attach the node to the current primary.
• Add new commands repmgr daemon start and repmgr daemon stop. Provides a standardized way of starting and stopping repmgrd.
• repmgr daemon status. Displays the node priority and the interval (in seconds) since the repmgrd instance last verified its upstream node was available.
• Add --compact option to repmgr cluster show. Makes it easier to copy the output as a compact table to emails, chats etc.
• repmgr cluster show. Differentiates between unreachable nodes and nodes which are running, but rejecting connections. This makes it possible to see whether a node is unreachable at network level, or if it is running but rejecting connections for some reason.
• Add --dry-run to repmgr standby promote.
• repmgr --version-number outputs the "raw" repmgr version number. Intended to be used by scripts, etc. when an easy parseable representation of the repmgr version is required.
• Add repmgr node check --data-directory-config options. Gives confirmation that repmgr is correctly configured.
• Add check to repmgr standby switchover. This ensures the data directory on the demotion candidate is configured correctly in repmgr.conf. Additionally, it ensures that repmgr, when remotely executed on the demotion candidate, can correctly verify that PostgreSQL was shut down cleanly on the demotion.

This major release includes several enhancements to repmgrd. For a detailed list of all changes, please read the complete release notes here.

Upgrading to this version is highly recommended for all repmgr users. Upgrade instructions are available here.

Packages and installation documentation are available via 2ndQuadrant’s public RPM and APT repositories from 2ndQuadrant here.

Source files can be downloaded here and installation instructions are available here.

repmgr is distributed under GPL v3.

For more information, please send an email to info@2ndQuadrant.com

What is Pgpool-II?

Pgpool-II is a tool to add useful features to PostgreSQL, including:

• connection pooling
• load balancing
• automatic fail over and more.

Minor releases

Pgpool Global Development Group is pleased to announce the availability of following versions of Pgpool-II:

• 4.0.4
• 3.7.9
• 3.6.16
• 3.5.20
• 3.4.23

Release notes for versions prior 3.6 are no longer included in the source code.

Please take a look at release notes.

You can download the source code and RPMs.

Oxford, United Kingdom - March 21, 2019

2ndQuadrant today announced the release of Barman version 2.7. This release fixes various bugs in backup parallel copy, geo-redundancy usability and UTF-8 input/output handling.

Barman (Backup and Recovery Manager) is an open source administration tool for managing backup and disaster recovery of PostgreSQL servers. It allows you to perform remote backups of multiple servers in business-critical environments and helps DBAs during the recovery phase.

Among the most outstanding changes of this release, Barman v2.7 fixes error handling during the parallel backup: previously an unrecoverable error during the copy could have corrupted the Barman internal state, requiring a manual kill of barman process with SIGTERM and a manual cleanup of the running backup in PostgreSQL.

Bug fixes for the geo-redundancy feature included in this release are:

• Ignore history/backup/partial files for the first sync
• Fix cron break due to network failure during sync, that did not allow subsequent tasks to be executed

We strongly recommend upgrading to Barman v2.7 at the earliest opportunity available. For this release, a simple package upgrade is required.

A complete list of changes and bug fixes is available here.

Download and installation instructions are available here.

Source files are available for download here.

Barman is developed and maintained by 2ndQuadrant and distributed under GPL v3.

For more information, please send an email to info@2ndQuadrant.com

Release of temboard 3.0, the powerful PostgreSQL management tool developed inside Dalibo Labs!

New feature: Maintenance

The maintenance plugin gives the users an overview on the databases, schemas, tables or indexes respective sizes. It is very useful to get information about bloat and toast. It helps users determine potential issues and understand or prevent performance issues due to unaccordingly used space. The plugin also provides easy access to maintenance actions such as VACUUM, ANALYZE or REINDEX in order to fix space or performance problems.

More about the maintenance plugin.

Enhancement of the interface

temboard’s interface is still improving. The 3.0 version lays out the instances as a grid on the homepage in order to better manage large database fleet. The sidebar is now collapsible to put forward the page's content. Moreover the homepage and the dashboard can be displayed in full screen mode which is more suitable when using a supervision screen.

And more...

Many other improvements and bug fixes are included, among which: * Limit double authentication to not read only APIs, * New monitoring probes: replication lag and connection, temporary files, * Show number of waiting/blocking req in activity tabs, * pg_hba.conf and pg_ident.conf edition removed from pgconf plugin.

More about this version's CHANGELOG.

An easier installation

Installing temboard and its agent is simpler thanks to its auto configuration script and clean documentation. The rpm and debian packages are available in the Dalibo Labs deposits.

Find out more information in the online documentation of temboard.

Video demo

You can find the demo for this new version of temboard on our Youtube page. Watch it by clicking here

Links

• Website: http://dali.bo/temboard
• GitHub: https://github.com/dalibo/temboard

temboard is mainly developed by Julien Tachoires, Étienne Bersac and Pierre Giraud.

EMS Software Development, one of the leaders in database administration software development, is pleased to announce the release of its new product SQL Backup for PostgreSQL for creating automatic backups for PostgreSQL databases. The tool offers easy and quick deployment of scheduled backup tasks on multiple servers and monitoring their execution.

“SQL Backup for PostgreSQL can significantly improve the workflow of database administrators in both large and small companies. They get the reliable tool to create automated backup tasks. The single console for managing backups for all servers at hand can considerably reduce costs on server maintenance ”- said Vladimir Sokolov, CEO of EMS Software Development.

“We have designed smart wizards to create scheduled backup tasks that can considerably save time on creating backups in large systems. SQL Backup for PostgreSQL can reduce storage costs due to direct uploading of backup files into popular cloud storages, such as Dropbox, Google Drive, Amazon S3 and others, Now we are focusing on adding new features and further development of the program “ - stated Ivan Proshechkin, technical director.

Regular execution of backup tasks with SQL Backup for PostgreSQL is a key for smooth and high-performance working of your PostgreSQL servers.

More information about SQL Backup for PostgreSQL.

We are very glad to announce the 3.0.0 version of E-Maj.

E-Maj is a PostgreSQL extension which enables fine-grained write logging and time travel on subsets of the database.

This version doesn't contain new big features. But:

• As the project is now an official member of the DaliboLabs constellation, the development is now supported by Dalibo,
• It is possible to install the PostgreSQL extension on PGaaS cloud environments where creating external EXTENSIONs is not allowed,
• the Emaj_web client has been largely improved, with a new GUI (while the old phpPgAdmin plugin is not maintained anymore).

This new version supports from 9.5 to v11 PostgreSQL versions.

The full documentation is available on line. The core extension is available at pgxn.org or github.org.

The Emaj_web application is also available at github.org.

Have fun with E-Maj !

The event will take place June 24-26 at the Sheraton Boston Hotel in Boston, MA, USA

Business leaders, database professionals, and developers are encouraged to submit individual presentations or panel discussions that highlight real-world enterprise-scale case studies, deep dives into Postgres tools and technologies, and explorations of the future of the database project.

The Call for Papers for Postgres Vision 2019 will end on Wednesday, April 10th.

Submit Your Paper Today at: http://go.enterprisedb.com/s0920nE00L2s0A000000i0B

Info and registration at: https://postgresvision.com/

The PostgreSQL Project is excited to announce that we have been accepted by Google to participate in their Summer of Code (GSoC) 2019 educational sponsoring program. GSoC is a program in which Google awards stipends to university students who complete a free and open-source software project during the summer. This will be the 12th time that the PostgreSQL Project will provide mentoring to university students to help develop new features for The World's Most Advanced Open Source Relational Database and related projects. We have the chance to accept student projects that will be developed from May to August.

For more information about GSoC, please visit the GSoC website: https://summerofcode.withgoogle.com/

For more information about working with the PostgreSQL project as part of GSoC, please visit our GSoC website: https://wiki.postgresql.org/wiki/GSoC

A new release is available for the Postgres Operator. The operator helps you to manage PostgreSQL HA clusters on Kubernetes. Notable changes among others are:

• support for setting shmem for better parallel query support
• support init containers
• improved logging in rolling upgrade
• added superuser team support (additional team to be created as superuser)
• support setting additional replication slots via Patroni
• fix issue surrounding delete cluster
• fix reporting .status

Thanks to everyone involved, reporting bugs, suggesting enhancements and contributing to the operator!

dbMigration .NET v10.1 is a simple, easy and intuitive multiple database migration and sync tool, With it you can easily migrate schema and data to PostgreSQL and vice versa without complicated procedures. (Free, All-In-One, Portable, Single executable file and Multi-language)

Major New features and improvements from version 9.2 to 10.1:

• PostgreSQL 11 support
• Added Auto-generating COMMENTS of tables and columns
• Added Auto-generating DEFAULT values of columns
• Added Auto-generating CHECK constraints of tables
• Added SSH: Secure Shell support
• Improved Graphical User Interface
• Improved Mapping column names from the target table
• Improved Automatic Mapping Types
• Improved Custom Mapping Types
• Improved Command-Line
• Improved Connection profile
• Compatible with Microsoft Windows 10 Insider Preview 18305 and higher
• ...and more

The new version is immediately available for download.