PostreSQL.org

The JDBC team has released version 42.2.12

We have released 42.2.12 to correct regressions in this version: Specifically - PR 1729 was reverted as this is a breaking change - PR 1719 has been reverted as it introduced errors in the PgType Cache

We suggest not using 42.2.11

JDBC Team

The PostgreSQL Community Code of Conduct Committee has delivered their Annual Report summarizing the complaints received and actions taken in the calendar year 2019.

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/2019/

Users had often asked where they could find older versions of packages from apt.postgresql.org. I had been collecting these since about April 2013, and in July 2016, I made the packages available via an ad-hoc URL on the repository master host, called "the morgue". There was little repository structure, all files belonging to a source package were stuffed into a single directory, no matter what distribution they belonged to. Besides this not being particularly accessible for users, the main problem was the ever-increasing need for more disk space on the repository host. We are now at 175 GB for the archive, of which 152 GB is for the morgue.

Our friends from yum.postgresql.org have had a proper archive host (yum-archive.postgresql.org) for some time already, so it was about time to follow suit and implement a proper archive for apt.postgresql.org as well, usable from apt.

So here it is: apt-archive.postgresql.org

The archive covers all past and current Debian and Ubuntu distributions. The apt sources.lists entries are similar to the main repository, just with "-archive" appended to the host name and the distribution:

deb https://apt-archive.postgresql.org/pub/repos/apt DIST-pgdg-archive main deb-src https://apt-archive.postgresql.org/pub/repos/apt DIST-pgdg-archive main

The oldest PostgreSQL server versions covered there are 8.2.23, 8.3.23, 8.4.17, 9.0.13, 9.1.9, 9.2.4, 9.3beta1, and everything newer.

Some example:

$ apt-cache policy postgresql-12 postgresql-12: Installed: 12.2-2.pgdg+1+b1 Candidate: 12.2-2.pgdg+1+b1 Version table: *** 12.2-2.pgdg+1+b1 500 500 http://apt.postgresql.org/pub/repos/apt sid-pgdg/main amd64 Packages 500 https://apt-archive.postgresql.org/pub/repos/apt sid-pgdg-archive/main amd64 Packages 100 /var/lib/dpkg/status 12.2-2.pgdg+1 500 500 https://apt-archive.postgresql.org/pub/repos/apt sid-pgdg-archive/main amd64 Packages 12.2-1.pgdg+1 500 500 https://apt-archive.postgresql.org/pub/repos/apt sid-pgdg-archive/main amd64 Packages 12.1-2.pgdg+1 500 500 https://apt-archive.postgresql.org/pub/repos/apt sid-pgdg-archive/main amd64 Packages 12.1-1.pgdg+1 500 500 https://apt-archive.postgresql.org/pub/repos/apt sid-pgdg-archive/main amd64 Packages 12.0-2.pgdg+1 500 500 https://apt-archive.postgresql.org/pub/repos/apt sid-pgdg-archive/main amd64 Packages 12.0-1.pgdg+1 500 500 https://apt-archive.postgresql.org/pub/repos/apt sid-pgdg-archive/main amd64 Packages 12~rc1-1.pgdg+1 500 500 https://apt-archive.postgresql.org/pub/repos/apt sid-pgdg-archive/main amd64 Packages 12~beta4-1.pgdg+1 500 500 https://apt-archive.postgresql.org/pub/repos/apt sid-pgdg-archive/main amd64 Packages 12~beta3-1.pgdg+1 500 500 https://apt-archive.postgresql.org/pub/repos/apt sid-pgdg-archive/main amd64 Packages 12~beta2-1.pgdg+1 500 500 https://apt-archive.postgresql.org/pub/repos/apt sid-pgdg-archive/main amd64 Packages 12~beta1-1.pgdg+1 500 500 https://apt-archive.postgresql.org/pub/repos/apt sid-pgdg-archive/main amd64 Packages

Because this is hosted on S3, browsing directories is only supported indirectly by static index.html files, so if you want to look at some specific URL, append "/index.html" to see it.

The archive is powered by a PostgreSQL database and a bunch of python/shell scripts, from which the apt index files are built.

Archiving old distributions

I'm also using the opportunity to remove some long-retired distributions from the main repository host. The following distributions have been moved over:

• Debian etch (4.0)
• Debian lenny (5.0)
• Debian squeeze (6.0)
• Ubuntu lucid (10.04)
• Ubuntu saucy (13.10)
• Ubuntu utopic (14.10)
• Ubuntu wily (15.10)
• Ubuntu zesty (17.04)
• Ubuntu cosmic (18.10)

They are available as "DIST-pgdg" from the archive, e.g. squeeze:

deb https://apt-archive.postgresql.org/pub/repos/apt squeeze-pgdg main deb-src https://apt-archive.postgresql.org/pub/repos/apt squeeze-pgdg main

pgagroal 0.5.0

March 17, 2020.

The pgagroal community is happy to announce version 0.5.0.

New features

• SCRAM-SHA-256 support
• Log connections
• Cancel shutdown
• Enable / disable database access
• Allow user connections during prefill

Plus various improvements and bug fixes.

pgagroal

pgagroal is a high-performance protocol-native connection pool for PostgreSQL.

Features

• High performance
• Connection pool
• Limit connections for users and databases
• Prefill support
• Remove idle connections
• Perform connection validation
• Enable / disable database access
• Graceful / fast shutdown
• Daemon mode
• User vault

Learn more on our web site or GitHub. Follow on Twitter.

pgagroal is released under the 3-clause BSD license, and is sponsored by Red Hat.

Mons, Belgium, March 16, 2020

check_pgbackrest is designed to monitor pgBackRest backups from Nagios, relying on the status information given by the info command.

It allows to monitor the backups retention and the consistency of the archived WAL segments.

Changes in check_pgbackrest 1.8

• Change output of missing archives. The complete list is now only shown in --debug mode (suggested by Guillaume Lelarge).
• Add --list-archives argument to print the list of all the archived WAL segments.

Links & Credits

check_pgbackrest is part of the Dalibo Labs initiative. It is mainly developed by Stefan Fercot. This is an open project, licensed under the PostgreSQL license. Any contribution to improve it is welcome.

Links:

• [Download]: https://github.com/dalibo/check_pgbackrest/releases
• [Support]: https://github.com/dalibo/check_pgbackrest/issues

We are very glad to announce the 3.3.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.

The major new feature introduced in this version is the ability to export and import parameters or tables groups configurations to or from JSON formatted files. This helps distributing full E-Maj environments on other databases.

The Emaj_web web client has been enhanced to take benefit from these features. A new page also reports details about an in progress or a completed E-Maj rollback operation.

The version also includes some fixes.

This new version supports from 9.5 to v12 PostgreSQL versions.

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

The Emaj_web client is also available at github.org.

Have fun with E-Maj !

The PostgreSQL Project is excited to announce that we have been accepted to participate in the Google Summer of Code (GSoC) program for the 13th time.

The GSoC program focuses on introducing students to Open Source software development by awarding stipends to university students who complete a free and open-source software project during their break from university. Students will propose a project and work with mentors from the PostgreSQL Community to complete that project over the course of three months, from May until August.

In order for PostgreSQL’s GSoC 2020 program to be successful, we need both students and mentors. If you are interested in being a mentor, please contact (Stephen Frost, sfrost@snowman.net).

Students should be sure to review the requirements at the GSoC website:

https://summerofcode.withgoogle.com/

After reviewing the guidelines and requirements, students should reach out through one of the community channels, which include IRC, Slack, and the mailing lists, information about which is available here:

https://www.postgresql.org/community/

Note that there is a dedicated gsoc2020-students channel on Slack, while on IRC the general #postgresql channel can be used. Regarding modifications to PostgreSQL core, the pgsql-hackers mailing list is best, and for sub-projects, please use their appropriate list.

Students may also reach out directly to mentors of projects they are interested in. Note that a student may propose any project they wish that meets the GSoC guidelines - so don’t feel limited to choosing one from the list if you have a great idea for how to improve PostgreSQL or other Open Source Software projects in the PostgreSQL ecosystem.

The full GSoC 2020 timeline is available here:

https://summerofcode.withgoogle.com/how-it-works/#timeline

We invite students and mentors to join and work together on enhancing the PostgreSQL ecosystem.

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

https://wiki.postgresql.org/wiki/GSoC

PostgreSQL Automatic Failover (PAF) v2.3.0 has been released on March 9th 2020 under the PostgreSQL licence.

See: https://github.com/ClusterLabs/PAF/releases/tag/v2.3.0

Four years and a week after the first public release back in March 2016!

PAF is a PostgreSQL resource agent for Pacemaker. Its original aim is to keep PostgreSQL and Pacemaker administration clear, to keep things simple, very documented and powerful.

Pacemaker is the industry reference for High Availability with Linux. It allows various HA architectures and can handle various services, with dependencies and much more!

This release of PAF features:

• the support PostgreSQL 12
• Debian package use /var/run/postgres as pghost default value
• few minor fixes
• setting "recovery_template" is now forbidden with PostgreSQL 12!

Source code, releases, packages documentation, procedures and support are available on github:

• home: http://clusterlabs.github.io/PAF/
• docs: https://clusterlabs.github.io/PAF/documentation.html
• source: https://github.com/ClusterLabs/PAF
• releases: https://github.com/ClusterLabs/PAF/releases
• issues: https://github.com/clusterlabs/PAF/issues

Packages will be updated on PGDG repos soon.

Please, use github issues, pgsql-general@postgresql.org or users@clusterlabs.org mailing lists if you have questions.

Any feedback is welcomed.

Crunchy Data is pleased to announce the initial release of pg_featureserv. pg_featureserv is a lightweight, low-configuration RESTful web service that provides access to spatial data stored in PostGIS tables, as well as spatial processing capability based on PostGIS spatial functions.

The service API follows the OGC API for Features Version 1.0 standard. It extends the API to expose more of the powerful spatial capabilities of PostGIS.

The pg_featureserv software is made available under the Apache 2.0 License.

The team behind pg_featureserv welcomes questions, issues and contributions. Please use the projects Github Issues to coordinate.

Crunchy Data is proud to support the development and maintenance of pg_featureserv.

Links

• Crunchy Data: https://www.crunchydata.com
• OGC API: http://docs.opengeospatial.org/is/17-069r3/17-069r3.html
• GitHub: https://github.com/crunchydata/pg_featureserv
• Issues: https://github.com/crunchydata/pg_featureserv/issues

Eymoutiers, France, Mars 5, 2020

PostgreSQL Anonymizer is an extension that hides or replaces personally identifiable information (PII) or commercially sensitive data from a PostgreSQL database.

The extension supports 3 different anonymization strategies: Dynamic Masking, In-Place Anonymization and Anonymous Dumps. It also offers a large choice of Masking Functions: Substitution, Randomization, Faking, Pseudonymization, Partial Scrambling, Shuffling, Noise Addition and Generalization.

Pseudonymization

Pseudonymization functions are similar to the faking functions in the sense that they generate realistic values. The main difference is that pseudonymization is deterministic : the functions will always return the same fake value based on a seed and an optional salt.

# SELECT anon.pseudo_email('Alice','salt123'); pseudo_email ------------------- fcadell56@ucoz.ru # SELECT anon.pseudo_email('Alice','salt123'); pseudo_email ------------------- fcadell56@ucoz.ru

WARNING : Pseudonymization is often confused with anonymization but in fact they serve 2 different purposes. With pseudonymization, the real data can be rebuilt using the pseudo data and the masking rule. If an attacker gets access to these elements, he or she can easily re-identify some people using brute force or dictionary attacks. Therefore, you should protect any pseudonymized data with the same level of security that the original dataset. The GDPR makes it very clear that personal data which have undergone pseudonymization are still considered to be personal information.

Improved Anonymous Exports

The anon.dump() function was slow and unpractical. It is now deprecated and replace by a tool named pg_dump_anon that you can use like the regular pg_dump command:

$ pg_dump_anon -h localhost -U bob mydb > anonymous_dump.sql

It uses the same connections parameters that pg_dump. The PostgreSQL environment variables ($PGHOST, PGUSER, etc.) and .pgpass are supported. However the plain format is the only supported format. The other formats (custom, dir and tar) are not supported.

Detecting Hidden Identifiers

This extension makes it very easy to declare masking rules. But of course when you're creating an anonymization strategy, the hard part is to scan the database model to find which columns contains direct and indirect identifiers and then decide how these identifiers should be masked.

We now provide a detect() function that will search for common identifiers names based on a dictionary. For now, 2 dictionaries are available: English ('en_US') and French ('fr_FR'). By default the English dictionary is used:

# SELECT anon.detect('en_US'); table_name | column_name | identifiers_category | direct ------------+----------------+----------------------+-------- customer | CreditCard | creditcard | t customer | id | account_id | t vendor | Firstname | firstname | t

The identifier categories are based on the HIPAA classification.

How to Install

This extension is officially supported on PostgreSQL 9.6 and later.

On Red Hat / CentOS systems, you can install it from the

$ yum install postgresql_anonymizer12

Then add 'anon' in the shared_preload_libraries parameter of your postgresql.conf file. And restart your instance.

For other systems, check out the install documentation :

https://postgresql-anonymizer.readthedocs.io/en/latest/INSTALL/

WARNING: The project is at an early stage of development and should be used carefully.

Thanks

This release includes code, bugfixes and ideas from Sebastien Delobel, Sam Buckingham, Thomas Clark, Joe Auty, Pierre-Henri Dubois Amy and Olleg Samoylov.

Many thanks to them !

How to contribute

PostgreSQL Anonymizer is part of the Dalibo Labs initiative. It is mainly developed by Damien Clochard.

This is an open project, contributions are welcome. We need your feedback and ideas ! Let us know what you think of this tool, how it fits your needs and what features are missing.

If you want to help, you can find a list of Junior Jobs.

Crunchy Data is pleased to announce the initial release of pg_tileserv.

pg_tileserv is a PostGIS-only tile server written in Go. By restricting itself to only using PostGIS as a data source, pg_tileserv gains the following features:

• Automatic configuration. The server can discover and automatically publish as tiles sources all tables it has read access to: just point it at a PostgreSQL/PostGIS database.
• Full SQL flexibility. Using function layers, the server can run any SQL to generate tile outputs. Any data processing, feature filtering, or record aggregation that can be expressed in SQL, can be exposed as parameterized tile sources.
• Database security model. You can restrict access to tables and functions using standard database access control. This means you can also use advanced access control techniques, like row-level security to dynamically filter access based on the login role.

The pg_tileserv is made available under the Apache 2.0 License.

The team behind pg_tileserv welcomes questions, issues and contributions. Please use the projects Github Issues to coordinate.

Crunchy Data is proud to support the development and maintenance of pg_tileserv.

Links

• GitHub: https://github.com/crunchydata/pg_tileserv
• Issues: https://github.com/crunchydata/pg_tileserv/issues
• Documentation: https://access.crunchydata.com/documentation/pg_tileserv
• Crunchy Data: https://www.crunchydata.com

dbMigration .NET v12.0 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 11.2 to 12.0:

• Added support for Adding prefix and suffix to tables
• Added support for High DPI scaling (100%~300%+)
• Added support for collations of PostgreSQL in Column Designer
• Added support for Identity types(BY DEFAULT/ALWAYS) of PostgreSQL in Column Designer
• Added support for PostgreSQL 8.0 (Compatible with Amazone Redshift)
• Added support for DOMAIN objects
• Improved and Fixed Automatic Mapping Types
• Improved Graphical User Interface
• Performance improvements
• ...and more

The new version is immediately available for download.

PostgreSQL Partition Manager (pg_partman) v4.3.0 has been released. This release contains important bug fixes for handling foreign keys and retention. Major new features include:

• A set of documentation for migrating an old trigger-based partition set to the native, declarative partitioning in PostgreSQL 11 or greater. Crunchy Data has also published this documentation as a blog post: https://info.crunchydata.com/blog/how-to-migrate-from-trigger-based-partitioning-to-native-in-postgresql
• A table matrix in the documentation to more clearly outline which partition set properties are handled via inheritance from the parent table vs the template table feature of pg_partman. The template table is for assisting with partitioning features that are not yet handled fully with native partitioning: https://github.com/pgpartman/pg_partman/blob/master/doc/pg_partman.md#child-table-property-inheritance
• A function for dumping out your pg_partman configuration for use when restoring a dump to another database. Thanks to James Coleman for this feature.
• A function to backfill gaps in the child tables that may occur for various reasons during ongoing maintenance.

Links

• Website - https://github.com/pgpartman/pg_partman
• Installation - https://github.com/pgpartman/pg_partman#installation
• Documentation - https://github.com/pgpartman/pg_partman/blob/master/doc/pg_partman.md
• Release Notes - https://github.com/pgpartman/pg_partman/blob/master/CHANGELOG.txt

Crunchy Data is proud to support the development and maintenance of pg_partman.

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.1.1
• 4.0.8
• 3.7.13
• 3.6.20
• 3.5.24

Major releases

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

• 4.1.0

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 - February 19, 2020

2ndQuadrant is proud to announce the release of pglogical 2.3, the next generation in logical replication for PostgreSQL. This release includes support for PostgreSQL 12, the latest major release of the world's most advanced open source database.

Implemented entirely as a PostgreSQL extension, pglogical is a logical replication system that serves as a highly efficient method of replicating data as an alternative to physical replication.

This release presents important enhancements and fixes including:

• Allow replicating tables and sequences to different names on the target node
• Add option to only synchronize the structure of replicated relations
• Add a new "force_text _transfer" subscription option
• Allow tables to be resynchronized in state SYNC_STATUS_SYNCDONE
• Fix pglogical_wait_for_sync_complete with unknown table

Download and installation instructions are available here.

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

The PostgreSQL Global Development Group has released an update to all supported versions of our database system, including 12.2, 11.7, 10.12, 9.6.17, 9.5.21, and 9.4.26. This release fixes one security issue found in the PostgreSQL server and over 75 bugs reported over the last three months.

Users should plan to update as soon as possible.

PostgreSQL 9.4 Now EOL

This is the last release for PostgreSQL 9.4, which will no longer receive security updates and bug fixes. PostgreSQL 9.4 introduced new features such as JSONB support, the ALTER SYSTEM command, the ability to stream logical changes to an output plugin, and more.

While we are very proud of this release, these features are also found in newer versions of PostgreSQL. Many of these features have also received improvements, and, per our versioning policy, it is time to retire PostgreSQL 9.4.

To receive continued support, we suggest that you make plans to upgrade to a newer, supported version of PostgreSQL. Please see the PostgreSQL versioning policy for more information.

Security Issues

• CVE-2020-1720: ALTER ... DEPENDS ON EXTENSION is missing authorization checks.

Versions Affected: 9.6 - 12

The ALTER ... DEPENDS ON EXTENSION sub-commands do not perform authorization checks, which can allow an unprivileged user to drop any function, procedure, materialized view, index, or trigger under certain conditions. This attack is possible if an administrator has installed an extension and an unprivileged user can CREATE, or an extension owner either executes DROP EXTENSION predictably or can be convinced to execute DROP EXTENSION.

The PostgreSQL project thanks Tom Lane for reporting this problem.

Bug Fixes and Improvements

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

Some of these fixes include:

• Fix for partitioned tables with foreign-key references where TRUNCATE ... CASCADE would not remove all data. If you have previously used TRUNCATE ... CASCADE on a partitioned table with foreign-key references please see the "Updating" section for verification and cleanup steps.
• Fix failure to add foreign key constraints to table with sub-partitions (aka a multi-level partitioned table). If you have previously used this functionality, you can fix it by either detaching and re-attaching the affected partition, or by dropping and re-adding the foreign key constraint to the parent table. You can find more information on how to perform these steps in the ALTER TABLE documentation.
• Fix performance issue for partitioned tables introduced by the fix for CVE-2017-7484 that now allows the planner to use statistics on a child table for a column that the user is granted access to on the parent table when the query contains a leaky operator.
• Several other fixes and changes for partitioned tables, including disallowing partition key expressions that return pseudo-types, such as RECORD.
• Fix for logical replication subscribers for executing per-column UPDATE triggers.
• Fix for several crashes and failures for logical replication subscribers and publishers.
• Improve efficiency of logical replication with REPLICA IDENTITY FULL.
• Ensure that calling pg_replication_slot_advance() on a physical replication slot will persist changes across restarts.
• Several fixes for the walsender processes.
• Improve performance of hash joins with very large inner relations.
• Fix placement of "Subplans Removed" field in EXPLAIN output by placing it with its parent Append or MergeAppend plan.
• Several fixes for parallel query plans.
• Several fixes for query planner errors, including one that affected joins to single-row subqueries.
• Several fixes for MCV extend statistics, including one for incorrect estimation for OR clauses.
• Improve efficiency of parallel hash join on CPUs with many cores.
• Ignore the CONCURRENTLY option when performing an index creation, drop, or reindex on a temporary table.
• Fall back to non-parallel index builds when a parallelized CREATE INDEX has no free dynamic shared memory slots.
• Several fixes for GiST & GIN indexes.
• Fix possible crash in BRIN index operations with box, range and inet data types.
• Fix support for BRIN hypothetical indexes.
• Fix failure in ALTER TABLE when a column referenced in a GENERATED expression is added or changed in type earlier in the same ALTER TABLE statement.
• Fix handling of multiple AFTER ROW triggers on a foreign table.
• Fix off-by-one result for EXTRACT(ISOYEAR FROM timestamp) for BC dates.
• Prevent unwanted lowercasing and truncation of RADIUS authentication parameters in the pg_hba.conf file.
• Several fixes for GSSAPI support, including having libpq accept all GSS-related connection parameters even if the GSSAPI code is not compiled in.
• Several fixes for pg_dump and pg_restore when run in parallel mode.
• Fix crash with postgres_fdw when trying to execute a remote query on the remote server such as UPDATE remote_tab SET (x,y) = (SELECT ...).
• Disallow NULL category values in the crosstab() function of contrib/tablefunc to prevent crashes.
• Several fixes for Windows, including a race condition that could cause timing oddities with NOTIFY.
• Several ecpg fixes.

For the full list of changes available, please review the release notes.

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.

If you had previously executed TRUNCATE ... CASCADE on a sub-partition of a partitioned table, and the partitioned table has a foreign-key reference from another table, you may have to execute the TRUNCATE on the other table, or execute a DELETE if you have added rows since running TRUNCATE ... CASCADE. The issue that caused this is fixed in this release, but you will have to perform this step to ensure all of your data is cleaned up.

For more details, please see the release notes.

Links

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

The PostgreSQL JDBC team is happy to announce the latest release. Don't let the release date fool you. We had troubles with signing the release and it took us a while to figure it out. This is mostly a bugfix release:

Notably:

• Cleanup PGProperty, sort values, and add some missing to docs (#1686)
• Fixing LocalTime rounding (losing precision) (#1570)
• Network Performance of PgDatabaseMetaData.getTypeInfo() method (#1668)
• Issue #1680 updating a boolean field requires special handling to set it to t or f instead of true or false (#1682)
• bug in pgstream for replication (#1681)
• Issue #1677 NumberFormatException when fetching PGInterval with small value (#1678)
• Metadata queries improvements with large schemas. (#1673)
• Utf 8 encoding optimizations (#1444)
• interval overflow (#1658)
• Issue #1482 where the port was being added to the GSSAPI service name (#1651)
• remove receiving EOF from backend after cancel since according to protocol the server closes the connection once
• cancel is sent (connection reset exception is always thrown) (#1641)
• Unable to register out parameter Issue #1646 (#1648)

see Changelog for details

pg_probackup is a utility to manage backup and recovery of PostgreSQL database cluster. It is designed to perform periodic full and incremental page-level backups of the PostgreSQL instance that enable you to restore the server in case of a failure.

Notable changes since pg_probackup 2.2.5

Bugfixes:

• pinned backups are now ignored for the purpose of WAL archive retention policy fulfillment. Reported by Vasily Puchkov.
• pgdata_bytes attribute for FULL and DELTA backups in remote mode is calculated correctly now.
• now full names of WAL segments are used in Max Segno, Min Segno and lost-segments fields of the WAL Archive catalog. Reported by Nikolay Popov.
• fix segfault caused by the stack size limit. Reported by Petr Karezin.

Improvements:

• added support for extension ptrack 2.0
• packages for ALT Linux versions p7, p8 and p9 are available in the repository
• latest documentation is now available

Links & Credits

pg_probackup is an open source tool developed by Postgres Professional under Postgres license. Main contributors are Artur Zakirov, Grigory Smolkin and Anastasia Lubennikova. pg_probackup can be downloaded at https://github.com/postgrespro/pg_probackup.

RazorSQL 9, an SQL editor, database query tool, database browser, and database administration tool, is now available for Windows, Mac, and Linux. Using RazorSQL, users can query, edit, browse, and manage dozens of databases from one tool. RazorSQL supports over 40 databases, including PostgreSQL. Connect to other databases via JDBC or ODBC (Windows only). Users can also use the built in relational database engine for their database needs.

Some of the main features contained in RazorSQL are visual tools for creating, editing, describing, altering, dropping, and viewing database objects such as tables, views, indexes, procedures, functions, and triggers; tools for importing and exporting data in various formats such as MS Excel, delimited files, SQL insert statements, HTML, XML, JSON, and text; a database browser for the viewing of database objects and structures; search tools for searching for database objects and database data, tools for building SQL queries and generating SQL and DDL, a database conversion tool for converting database table structures and data from one database type to another, a SQL formatting tool, SQL history tracking and and SQL favorites tool for storing frequently used SQL statements, and a programming editor and query tool with support for SQL, PL/SQL, TransactSQL, SQL PL, PHP, Java, XML, HTML, and many other programming languages that features tools for searching and replacing data, programmable macros, coding sidekicks for various programming languages, a file system browser, function and method browsers, and much more.

Version 9 adds support for creating, editing, and viewing PostgreSQL and Redshift stored procedures and improvements to the import tool and database conversion tool.

Versions of RazorSQL are available for Windows, macOS, Mac OS X, Linux, and Solaris.

RazorSQL 9 is available for immediate download at https://razorsql.com/

More Info: https://razorsql.com/

Download URL: https://razorsql.com/download.html

Change Log: https://razorsql.com/updates.html

Crunchy Data is pleased to announce the initial release of pgbouncer_fdw

pgbouncer_fdw provides a direct SQL interface to the pgbouncer SHOW commands. It takes advantage of the dblink_fdw feature to provide a more typical, table-like interface to the current status of your pgbouncer server(s). This makes it easier to set up monitoring or other services that require direct access to pgbouncer statistics.

A blog post about pgbouncer_fdw has been published recently as well, going over what lead to the development of this tool as well as some brief examples:

https://info.crunchydata.com/blog/making-pgbouncer-easier-to-monitor

The pgbouncer_fdw is made available under the PostgreSQL License.

The team behind pgbouncer_fdw welcomes questions, issues and contributions. Please use the projects GitHub issues to coordinate.

Links

• pgobouncer_fdw project website
• Documentation
• Release notes

Crunchy Data is proud to support the development and maintenance of pgbouncer_fdw.