PostreSQL.org

The PostgreSQL Community Code of Conduct Committee is approaching its first year anniversary. As part of the Community CoC policy, the Committee membership is to be refreshed on an annual basis.

The Code of Conduct Committee is seeking up to two (2) volunteers to serve on the Committee for the coming year, October 1, 2019 - September 30, 2020. The Committee is seeking people who reflect the diversity of the PostgreSQL community, with the goal to have members from multiple countries and varied demographics.

The time commitment for Committee involvement varies, based on internal administrative work and the number of active investigations. We estimate an average of 5 to 10 hours per month, but that could increase if there is an increase in the number of incident reports.

If you are interested, please complete the questionnaire below, and email your responses to the Committee at coc@postgresql.org no later than September 22, 2019, at 11:00 PM AOE. This has been extended from the original deadline.

You can check your local time against AOE at https://time.is/Anywhere_on_Earth

The questionnaire:

• Your name:
• Current employer:
• Current country of residence:

(We ask for employer and residence because one of the goals of the Committee is to have representation from a variety of geographical areas. We also want to avoid a concentration of members from one company.)

1. What interests you about being on the CoC Committee?
2. Have you been on another CoC Committee, or had a similar role at another organization? (Prior experience is not required, it's just helpful to know everyone's background.)
3. What else do you want to tell us about yourself that is helpful for us to know about your potential involvement with the CCoC Committee?

Thank you.

Regards,

Stacey Haysler, Chair, PostgreSQL Community Code of Conduct Committee

This release fixes a regression caused by PR 1526 which incorrectly mapped an inet column to an InetAddress object. The problem with this is that inet columns can contain networks as well as hosts. InetAddress does not know how to deal with a network.

PR 1568 fixes this and closes ISSUE 1567

Thanks to all who reported and provided the fix.

The PostgreSQL Global Development Group announces that the fourth 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.

This is likely the final beta release of PostgreSQL 12 before a release candidate is made available.

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.

Upgrading to PostgreSQL 12 Beta 4

To upgrade to PostgreSQL 12 Beta 4 from Beta 3 or an earlier version of PostgreSQL 12, you will need to use a strategy similar to upgrading between major versions of PostgreSQL (e.g. pg_upgrade or pg_dump / pg_restore). For more information, please visit the documentation section on upgrading.

Changes Since 12 Beta 3

There have been many bug fixes for PostgreSQL 12 reported during the Beta 3 period and applied to the Beta 4 release. This release also includes other bug fixes that were reported for supported versions of PostgreSQL that also affected PostgreSQL 12.

These changes include:

• Fix for crash that could occur with nested queries that contain locks
• Only allow chained transactions to work in an explicitly set transaction block, otherwise error
• Changed the log level for several types of messages around partitioning to DEBUG1
• Add the default_table_access_method configuration parameter to the sample configuration kept in postgresql.sample.conf
• Fix handling of duplicate entries in postgresql.auto.conf when ALTER SYSTEM is called. Now, when a configuration parameter with duplicate entries is updated, PostgreSQL will remove all entries and append the new entry to the end
• Ensure ALTER SYSTEM makes case-insensitive comparisons when adjusting entries in the configuration

For a detailed list of fixes, please visit the open items page.

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 fourth beta release of version 12. In all likelihood, this is the final beta release of PostgreSQL 12 before one or more release candidates are made available. 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
• Follow @postgresql on Twitter

PostgreSQL JDBC 42.2.7 has been released.

This release does not add any groundbreaking features, rather it fixes some annoying problems and makes life a little easier for some. See below for details.

Added

• Expose parameter status messages (GUC_REPORT) to the user PR 1435
• Add automatic module name to manifest for jdk9+ PR 1538
• Log ignoring rollback when no transaction in progress PR 1549
• Map inet type to InetAddress PR 1527 issue 1134

Fixed

• issue 1547 As long as peek returns some bytes do not reset the timeout, this allows us to continue checking until any async notifies are consumed PR 1548
• issue 1466 In logical decoding the if the backend was requesting a reply we… PR 1467
• issue 1534 Proleptic java.time support PR 1539
• Ensure isValid() will not last more than timeout seconds PR 1557

The JDBC team would like to thank all that helped with this release your input is invaluable.

pgDay Santiago 2019's Early Bird tickets are now being sold — get yours now!

pgDay Santiago is a non-profit, community-run conference in Santiago de Chile focused on PostgreSQL, that delivers one day packed with technical content and your chance to meet your local PostgreSQL peers. Come join us to learn, teach and have fun! Our first-ever pgDay will be held in Hotel Director Vitacura on October 29th.

Registration

Early Bird ticket sales are open until September 30th. Why wait?

Sponsors

We wouldn't be able to organize this without the support from our sponsors:

• 2ndQuadrant — https://2ndQuadrant.com/
• Vigigo — https://www.vigigo.com/

Sponsorship opportunities are still available! Please see our prospectus if would like to contribute to strengthening the Chilean PostgreSQL community.

The annual gathering of the PostgreSQL community in Down Under is just a couple of months away.

PostgreSQL Down Under (PGDU) is excited to bring to you the third edition of its annual conference, just days after the much-anticipated major release of PostgreSQL, version 12!

It’s our pleasure to invite you to speak at PGDU 2019 in Sydney.

Whether you are a seasoned speaker or thinking of speaking for the first time, PGDU offers you the opportunity to submit a paper.

In the past, we had talks covering:

• Case studies (Tell us how you are making use of PostgreSQL somewhere)
• Personal experiences (A day in the life of you and PostgreSQL)
• Tools and utilities (Tabs or Spaces? Want to stir debate or demonstrate your love publicly?)
• Migration stories (Maybe filed under Horror/Thriller, Comedy, Drama, or perhaps Action?)
• New & existing features (I love PostgreSQL because…)
• New feature development & vision (If only PostgreSQL would have … I will be ….)
• Benchmarks (Hail ye quants…)
• Performance & scaling (Put the pedal to the metal)
• Enterprise readiness (Security, backup & recovery, audit, compliance, etc)
• Lightning talks (tweets impersonated, 3-5 minutes)
• Facilitate a forum (suggest a topic)

Got an idea that doesn’t fit above, we are all ears!

You can choose between a 45-minute slot (with Q&A included) or a 5-minute lightning talk.

The Call for Papers is now open at the event website until 5 pm AEST on 5th October 2019. Important Dates:

• 09 Sep 2019 - Ticket sales commence
• 09 Sep 2019 - Call for papers open
• 05 Oct 2019 - Call for papers close
• 10 Oct 2019 - Presentation schedule announced
• 18 Oct 2019 - Final agenda
• 15 Nov 2019 - PGDU 2019

Venue:

Fishburners Sydney Level 2-3 11 York Street Sydney, NSW

(Google Maps)

Sponsorship:

This event would not be possible without generous sponsorship and support from many different organisations.

If you are interested in sponsoring or have any other inquiries, please send an email to pgdu-committee@lists.pgdu.org

Looking forward to your submissions.

PostgresOpen 2019 - Free Childcare, Closed Captioning, & More!

Greetings!

PostgresOpen is both the longest continuously running PostgreSQL conference and the only dedicated community recognized event in the United States. Our conference delivers two days packed with fantastic sessions all about PostgreSQL and related open source technologies, one day of extended workshops, and the usual hallway and social track. Our eighth annual conference will be held September 11th - 13th, 2019 in Orlando, Florida at the Rosen Centre Hotel.

Workshops will be on Wednesday, September 11th, with the main conference occurring on Thursday, September 12th - Friday, September 13th.

Registration for the conference is closing as the conference is happening in just 2 weeks! We will have on-site registration but it’s strongly recommended to register as soon as possible, as workshops have a limited number of slots available and some are just about filled to capacity already.

Be sure to choose the ones you’d like to attend before they’re full in order to reserve your spot -

https://2019.postgresopen.org/tickets/

Find the most up-to-date information and convenient links below with regards to PostgresOpen 2019!

Inclusion

We have several exciting updates around PostgresOpen 2019 - first of all, we’re offering free on-site childcare to ALL attendees from Sunshine Babysitting Hotel Childcare this year! Their team will be at the conference location from 8 AM - 5 PM on all three days, and they will be providing games, toys, snacks, and crafts. This is a perfect opportunity to visit the absolutely beautiful city of Orlando and bring your family along to visit Disney World, Universal, Harry Potter World, or the multitude of other fantastic options during the weekend following the conference.

Video recordings will be made for all sessions (not including workshops) and will be made available on YouTube after the conference, as per usual. We are excited to include closed captioning on all videos uploaded for the 2019 conference! Videos from past years of our conference can be found on our official PostgresOpen YouTube channel: https://www.youtube.com/PostgresOpen

Additionally, we are providing quiet rooms for both speakers and attendees. If you have work to do, need to make a phone call, or just need some space ~ regardless of the reason, a room will be available for that purpose.

Find out more information on all of these offerings and find out more information about how we’re supporting our attendees at PostgresOpen 2019 here!

https://2019.postgresopen.org/inclusion/

Our team here at PostgresOpen hope these actions will assist with making the event comfortable for everyone. If there's something more you think we could be doing, please get in touch through our primary email address - contact@postgresopen.org.

Venue

Our conference will be held at the fantastic Rosen Centre Hotel in Orlando, FL this year. Find hotel and airport information on our website, in addition to ideas for other interesting things to do while in Orlando.

We have extended the conference group rate for the hotel to September 4th! Be sure to book your rooms at the venue while they last at the discounted rate -

https://2019.postgresopen.org/venue/

Sessions

The PostgresOpen 2019 tutorials, workshops, and sessions have now been announced! Find the full list of sessions here:

https://postgresql.us/events/pgopen2019/sessions/

Or if you prefer to view a schedule, find it here:

https://postgresql.us/events/pgopen2019/schedule/

Sponsors & Sponsorship

As always, we wouldn't be able to put on these great events without the support of our sponsors. This year we are pleased to be able to recognize our Diamond sponsors:

• Microsoft - https://azure.microsoft.com/en-ca/services/postgresql/ @AzureDBPostgres
• Heroku - https://www.heroku.com/home @heroku
• EnterpriseDB - https://www.enterprisedb.com/ @EDBPostgres

Be sure to check out our site to see all of our Gold, Silver and Supporter sponsors:

https://2019.postgresopen.org/sponsors/

Sponsorship opportunities are still available - please visit https://2019.postgresopen.org/becomesponsor/ to review our prospectus. All funds for the conference will go towards providing a fantastic conference experience for our attendees, including enhancing accessibility for all, and all proceeds will go to support the non-profit United States PostgreSQL Association and future events. Support the PostgreSQL and open source communities through sponsorship of PostgresOpen 2019!

Contact Us

Please follow our social media accounts if you’re interested in additional information and updates about the conference!

• https://twitter.com/PostgresOpen
• https://www.facebook.com/postgresopen
• https://www.linkedin.com/company/postgresopen/

Any questions or concerns? We’d love to help - reach out to contact@postgresopen.org and we'll be happy to assist. Looking forward to seeing everyone in Orlando!

PostgreSQL Conference Europe is pleased to announce that the schedule for its 2019 event, to be held in Milan, Italy, from 15th – 18th October, has now been published.

The schedule is, of course, subject to minor changes.

PostgreSQL Conference Europe 2019 is the 11th annual PostgreSQL Conference Europe, previous events having been held in cities such as Lisbon, Warsaw, Tallinn, Vienna, Madrid, Dublin, Prague, and Amsterdam, attracting hundreds of PostgreSQL users and developers.

Tickets are still available here, subject to availability. With a history of the event selling out, and well over half the available tickets already sold, we encourage everybody who wants to attend to register as soon as possible to guarantee a seat.

We also still have seats left at some of the training sessions held the day before the main conference, taught by PostgreSQL experts from around the world. Available training sessions are listed here, and are booked along with the registration. Training attendees get a discount on the entry fee to the main conference.

Some further sponsorship opportunities are also still available, and provide a great opportunity for organisations to market themselves to the PostgreSQL community.

We look forward to seeing you in Milan!

PgBouncer 1.11.0 is out. The major new feature is support for SCRAM authentication.

This release also adds support for a new startup packet type introduced in PostgreSQL 12 (GSSENCRequest), so this release is recommended for a better experience with PostgreSQL 12 and beyond.

See

https://pgbouncer.github.io/2019/08/pgbouncer-1-11-0

for more information, the detailed changelog, and download links.

PgBouncer is a lightweight connection pooler for PostgreSQL.

Crunchy Data is pleased to announce the release of pg_partman 4.2.0, the latest version of the open source partition management PostgreSQL extension.

pg_partman 4.2 adds preliminary support for PostgreSQL 12 and introduces an important change to how UNLOGGED tables are managed in a partition set.

pg_partman is a PostgreSQL extension that helps you to manage both time series and serial-based table partition sets, including automatic management of partition creation and runtime maintenance. pg_partman works with the native partitioning introduced into PostgreSQL 10 so users can benefit from significant performance enhancements.

You can follow the instructions in the README to install pg_partman or use a preferred package manager of your choice.

Notable Changes

• pg_partman has added preliminary support for PostgreSQL 12, and will be dropping support for PostgreSQL 9.4 after PostgreSQL 12 is released.

• As of PostgreSQL 12, pg_partman will no longer support inheriting OIDs as this special column behavior has been removed.

• The UNLOGGED status of a partition set in native partitioning is now managed by the template table instead of the parent table.

Currently in PostgreSQL, setting a natively partitioned parent table as UNLOGGED/LOGGED is not a property that can be changed with an ALTER TABLE. If the state of UNLOGGED/LOGGED is subsequently changed on the parent table, it will not be passed on to new child tables.

If you believe you have child tables affected by this, you will have to fix them manually. If any of your native partition sets are UNLOGGED, be sure to set this property on the template table before upgrading to this version.

pg_partman will maintain this behavior until PostgreSQL determines a definitive way that UNLOGGED changes will be handled. For more information, please see: https://www.postgresql.org/message-id/flat/15954-b61523bed4b110c4%40postgresql.org

• Changed default option for the maintenance background worker running ANALYZE on child table creation to false for PostgreSQL 11 and later versions. If this is desired, please set the option pg_partman_bgw.analyze to true in your postgresql.conf.

Features

• Added new configuration option constraint_valid to the part_config(_sub) table to control whether the additional constraints that pg_partman can manage are added in a NOT VALID state. By default, the constraints are added as VALID as they were before. Note that if this config is changed to false, constraint exclusion will not work until the constraints are validated.

Fixes

• Fixed bug that prevented pg_partman from creating child tables in PostgreSQL 12 due to usage of pg_class.relhasoids column
• Fixed bug where primary key/unique indexes applied to pre-existing template tables were not being applied to the default partition that was added in PostgreSQL 11 native partitioning.
• Fixed bug that caused an error in the retention management of time-based partitioning sets. If retention would attempt to remove the last child table, maintenance would throw an error about a missing table instead of just a warning about the last table attempting to be dropped.
• Properly throw an error with create_parent() when the data type of the partition column is numeric. Previously, it would not report any errors but would also not add the proper data to the part_config table so future maintenance would not work.

Links

• Website
• Download
• Documentation
• Release Notes

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

dbMigration .NET v11.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 10.2 to 11.1:

• Added PostgreSQL 12 support
• Added TLS 1.1 and 1.2 support
• Added support for Computed Column Expression of PostgreSQL 12
• Added support for varbit(bit varying) data type of PostgreSQL
• Added Find in List
• Fixed an issue with connecting to PostgreSQL via PgBouncer
• Fixed an issue converting Decimal of Byte() on PostgreSQL
• Updated the target .NET Framework to 4.5.2
• Improved Graphical User Interface
• Improved Automatic Mapping Types
• Improved Custom Mapping Types
• Performance improvements
• Compatible with Microsoft Windows 10 (1903) and higher
• ...and more

The new version is immediately available for download.

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.6
• 3.7.11
• 3.6.18
• 3.5.22
• 3.4.25

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.

PostgresOpen 2019 - Discounted Hotel Rates, Open Registration, Sessions, & More

PostgresOpen is both the longest continuously running PostgreSQL conference and the only community recognized event in the United States. Our conference delivers two days packed with fantastic sessions all about PostgreSQL and related open source technologies, one day of extended workshops, and the usual hallway and social track. Our eighth annual conference will be held September 11th - 13th, 2019 in Orlando, Florida at the Rosen Centre Hotel.

Workshops will be on Wednesday, September 11th, with the main conference occurring on Thursday, September 12th - Friday, September 13th.

Find the most up-to-date information and convenient links below with regards to our conference!

Venue

Our conference will be held at the fantastic Rosen Centre Hotel in Orlando, FL this year. Find hotel and airport information on our website, in addition to ideas for other interesting things to do while in Orlando.

We have extended the conference group rate for the hotel to August 16th! Be sure to book your rooms at the venue while they last at the discounted rate -

https://2019.postgresopen.org/venue/

Registration

Regular registration for the conference is open! Be sure to register as soon as possible - workshops have a limited number of slots available. It’s also worthwhile to note we will have one workshop available for free thanks to one of our Diamond sponsors this year. Be sure to choose the ones you’d like to attend before they’re sold out in order to reserve your spot!

https://2019.postgresopen.org/tickets/

Sessions

The PostgresOpen 2019 tutorials, workshops, and sessions have now been announced! Find the full list of sessions here:

• https://postgresql.us/events/pgopen2019/sessions/

Or if you prefer to view a schedule, find it here:

• https://postgresql.us/events/pgopen2019/schedule/

Sponsors & Sponsorship

As always, we wouldn't be able to put on these great events without the support of our sponsors. This year we are pleased to be able to recognize our Diamond launch sponsors:

• Microsoft - https://azure.microsoft.com/en-ca/services/postgresql/ - @AzureDBPostgres
• Heroku - https://www.heroku.com/home - @heroku

Be sure to check out our site to see all of our Gold, Silver and Supporter sponsors: https://2019.postgresopen.org/sponsors/

Sponsorship opportunities are still available - please visit https://2019.postgresopen.org/becomesponsor/ to review our prospectus. All funds for the conference will go towards providing a fantastic conference experience for our attendees, including enhancing accessibility for all. Support the PostgreSQL and open source communities through sponsorship of PostgresOpen 2019!

Contact Us

Please follow our Twitter account if you’re interested in additional information and updates about the conference! https://twitter.com/PostgresOpen

Any questions or concerns? We’d love to help - reach out to contact@postgresopen.org and we'll be happy to assist. We look forward to seeing everyone in Orlando!

https://2019.postgresopen.org/

The PostgreSQL Global Development Group has released an update to all supported versions of our database system, including 11.5, 10.10, 9.6.15, 9.5.19, and 9.4.24, as well as the third beta of PostgreSQL 12. This release fixes two security issues in the PostgreSQL server, two security issues found in one of the PostgreSQL Windows installers, and over 40 bugs reported since the previous release.

Users should install these updates as soon as possible.

A Note on the PostgreSQL 12 Beta

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

Security Issues

Four security vulnerabilities have been closed by this release:

CVE-2019-10208: TYPE in pg_temp executes arbitrary SQL during SECURITY DEFINER execution

Versions Affected: 9.4 - 11

Given a suitable SECURITY DEFINER function, an attacker can execute arbitrary SQL under the identity of the function owner. An attack requires EXECUTE permission on the function, which must itself contain a function call having inexact argument type match. For example, length('foo'::varchar) and length('foo') are inexact, while length('foo'::text) is exact. As part of exploiting this vulnerability, the attacker uses CREATE DOMAIN to create a type in a pg_temp schema. The attack pattern and fix are similar to that for CVE-2007-2138.

Writing SECURITY DEFINER functions continues to require
following the considerations noted in the documentation:

https://www.postgresql.org/docs/current/sql-createfunction.html#SQL-CREATEFUNCTION-SECURITY

The PostgreSQL project thanks Tom Lane for reporting this problem.

CVE-2019-10209: Memory disclosure in cross-type comparison for hashed subplan

Versions Affected: 11

In a database containing hypothetical, user-defined hash equality operators, an attacker could read arbitrary bytes of server memory. For an attack to become possible, a superuser would need to create unusual operators. It is possible for operators not purpose-crafted for attack to have the properties that enable an attack, but we are not aware of specific examples.

The PostgreSQL project thanks Andreas Seltenreich for reporting this problem.

CVE-2019-10210: EnterpriseDB Windows installer writes PostgreSQL superuser password to unprotected temporary file

Versions Affected: The EnterpriseDB Windows installer for versions 9.4 - 11

The EnterpriseDB Windows installer writes a password to a temporary file in its installation directory, creates initial databases, and deletes the file. During those seconds while the file exists, a local attacker can read the PostgreSQL superuser password from the file.

The PostgreSQL project thanks Noah Misch for reporting this problem.

CVE-2019-10211: EnterpriseDB Windows installer bundled OpenSSL executes code from unprotected directory

Versions Affected: The EnterpriseDB Windows installer for versions 9.4 - 11

When the database server or libpq client library initializes SSL, libeay32.dll attempts to read configuration from a hard-coded directory. Typically, the directory does not exist, but any local user could create it and inject configuration. This configuration can direct OpenSSL to load and execute arbitrary code as the user running a PostgreSQL server or client. Most PostgreSQL client tools and libraries use libpq, and one can encounter this vulnerability by using any of them. This vulnerability is much like CVE-2019-5443, but it originated independently. One can work around the vulnerability by setting environment variable OPENSSL_CONF to "NUL:/openssl.cnf" or any other name that cannot exist as a file.

The PostgreSQL project thanks Daniel Gustafsson of the curl security team for reporting this problem.

Bug Fixes and Improvements

This update also fixes over 40 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:

• Fix for ALTER TABLE ... ALTER COLUMN TYPE when multiple column types are modified in a single-command. This issue was introduced in the previous cumulative update (11.4, 10.9, 9.6.14, 9.5.18, 9.4.23, and 12 beta 2).
• Ensure that partition key columns will not be dropped as the result of an "indirect drop," such as from a cascade from dropping the key column's data type (e.g. a custom data type). This fix is applied only to newly created partitioned tables: if you believe you have an affected partition table (e.g. one where the partition key uses a custom data type), you will need to either create a new table and move your data into it OR use pg_upgrade.
• Prevent dropping a partitioned table's trigger if there are pending trigger events in child partitions. This particularly affects foreign key constraints, which are implemented by triggers.
• Several additional fixes for partitioning, including a fix for partition pruning that could lead to inefficient queries.
• Fix for parallel hash joins that could lead to duplicate result rows in EXISTS queries.
• Several fixes for the query planner.
• Several fixes for issues that would lead to query deadlocks.
• Fix for multi-column foreign keys when rebuilding a foreign key constraint.
• Prevent extended statistics from being built for inherited tables.
• Fix for the canonicalization of date ranges that include -infinity/infinity endpoints to ensure the behavior matches the documentation.
• Fix loss of fractional digits when converting very large money values to numeric.
• Fix for PL/pgSQL functions that return composite types.
• Make libpq ignore the \r carriage return in connection service files, which was causing connection failures in some edge cases.
• Several fixes for psql, which includes avoiding incorrect tab completion options after SET variable =.
• Improve reliability of contrib/amcheck's index verification.
• Set initdb to prefer the timezone behavior defined by the C library instead of what is defined by localtime or posixrules. This ensures PostgreSQL uses the "real" timezone name instead of an artificial name.
• Fix pg_dump to ensure that custom operator classes are dumped in the correct order to prevent creating an unrestorable dump.
• Fix possible lockup in pgbench when using -R option.
• Fix spinlock assembly code for MIPS CPUs so that it works on MIPS r6.

This update also contains tzdata release 2019b for DST law changes in Brazil, plus historical corrections for Hong Kong, Italy, and Palestine. This update also adds support for zic's new -b slim option to reduce the size of the installed zone files, though it is not currently being used by PostgreSQL.

For more details, you can read the full copy of the release notes here:

https://www.postgresql.org/docs/release/

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.

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 third 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
• Release Notes
• Security Page
• Versioning Policy
• Beta Testing Information
• PostgreSQL 12 Beta Release Notes
• PostgreSQL 12 Open Issues
• Follow @postgresql on Twitter

Oxford, United Kingdom - August 1, 2019

2ndQuadrant today announced the release of Barman version 2.9.

This release introduces native support for PostgreSQL 12, which includes major changes in the way Point-In-Time-Recovery and Replicas are managed. For older versions of PostgreSQL (11 and earlier), Barman still maps its configuration and run-time options to the underlying PostgreSQL system, using the traditional recovery.conf based method, whilst using the new GUCs for version 12 (and future versions).

Barman v2.9 presents experimental support for JSON output of Barman commands, facilitating integration with external monitoring and management tools. It also includes various UI improvements and bug fixes.

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.

The most relevant changes included in this release are listed below:

• Support for PostgreSQL 12 by supporting the new way of managing recovery and standby settings through GUC options and signal files (recovery.signal and standby.signal)
• Add --bwlimit command line option to set bandwidth limitation for backup and recover commands.
• Ignore WAL archive failure for check command in case the latest backup is WAITING_ FOR_WALS
• Add --target-lsn option to set recovery target Log Sequence Number for recover command with PostgreSQL 10 or higher
• Add --spool-dir option to barman-wal-restore so that users can change the spool directory location from the default, avoiding conflicts in case of multiple PostgreSQL instances on the same server.
• Rename barman_ xlog directory to barman_wal
• JSON output writer to export command output as JSON objects to facilitate integration with external tools and systems. (Experimental in this release)

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

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

PostgresOpen 2019 Sessions Announced, Last Week for Early Bird!

PostgresOpen is a non–profit, community–run conference series in the United States focused on PostgreSQL. Our conference delivers two days packed with tutorials and presentations about PostgreSQL and related technologies, one day of extended trainings, and the usual hallway and social track. Our eighth annual conference will be held September 11th - 13th, 2019 in Orlando, Florida at the Rosen Centre Hotel.

Tutorials and workshops will be on Wednesday, September 11th, with the main conference occurring on Thursday, September 12th - Friday, September 13th.

Sessions

The PostgresOpen 2019 tutorials, workshops, and sessions have now been announced and are available here:

• https://postgresql.us/events/pgopen2019/sessions/

Our newly published schedule can be found here:

• https://postgresql.us/events/pgopen2019/schedule/

Registration

We've extended Early Bird registration until August 2nd, but that's less than a week away! Be sure to register for the conference and choose the tutorials and workshops you'd like to attend before they're sold out:

• https://2019.postgresopen.org/tickets/

Venue

Our venue and recommended hotel this year is the fantastic Rosen Centre Hotel in Orlando, FL. Please be sure and book your stay using our conference discount by going through the Venue & Hotel page:

• https://2019.postgresopen.org/venue/

Sponsors & Sponsorship

As always, we wouldn't be able to put on these great events without the support of our sponsors. This year we are pleased to be able to recognize our Diamond launch sponsors:

• Microsoft - https://azure.microsoft.com/en-ca/services/postgresql/
• Heroku - https://www.heroku.com/home

Be sure to check out our site to see all of our Gold, Silver and Supporter sponsors: https://2019.postgresopen.org/sponsors/

Sponsorship opportunities are still available! Please visit https://2019.postgresopen.org/becomesponsor/ to review our prospectus.

Contact Us

Finally, for frequent updates and information related to our conference, please follow our Twitter account: https://twitter.com/PostgresOpen

Any questions? Please contact us at contact@postgresopen.org and we'll be happy to assist. We look forward to seeing everyone in Orlando!

https://2019.postgresopen.org/

We are happy to annouce a new release of the Postgres Operator. Notable changes among others are:

• New browser-based UI to manage Postgres clusters
• Operator can create cron jobs for logical backups
• Initialize standby cluster from WAL archive in S3 bucket
• Provide manifests for user-facing clusterroles
• New end-2-end test suite using kind
• New deployment options: Helm chart, Kustomization and OLM

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

Oxford, United Kingdom - July 25, 2019

2ndQuadrant is proud to announce the release of pglogical 2.2.2, the next generation in logical replication for PostgreSQL. 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 is a maintenance release that adds a few minor features and fixes some known issues:

• Support for replication of tables which have covering unique indexes.
• Improve failover slot detection.
• Improve tests of column filtering and row filtering
• Fix error messages to conform better to PostgreSQL standard.
• Fix crash in DDL replication when parallelization is used when executing the DDL on subscriber.

Download and installation instructions are available here.

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

PostgreSQL Conference Europe 2019 in Milan, Italy, on October 15-18 is now open for registrations.

Early Bird discounted tickets are available until September 1st. However, as they are limited to 75 tickets, only a few are still left! Register quickly if you want to secure one of them!

The Tuesday training sessions have also been finalized, and are now available for registration. Six sessions in a mix of full and half day sessions are available:

• PostgreSQL Business Continuity
• The PostgreSQL Optimizer and indexes unleashed
• Migration to PostgreSQL
• PostgreSQL Security
• Implementing your first Postgres extension: from coding to distribution
• The "default" postgresql.config, step by step

See the website for more details!

Training sessions are available at an extra cost of €150 per half day. Attendees of training sessions will also receive a €90 discount on the regular conference fee. Seats to these sessions are limited to smaller groups, so make sure you register early!

Our call for papers is still open! If you have already submitted a talk, or are planning to submit one, we suggest you wait to register until you have received a confirmation if the talk was accepted or not. If your talk is accepted, attendance is of course free!

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.

Please submit your proposals by going to the submission form 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.

And finally, our Call for Sponsors is also still open. Our Platinum sponsor slots are sold out at this time, but we have free slots at all other levels remaining. Take your chance to present your services or products to the PostgreSQL community. All sponsorship levels also include one or more free entrance tickets, depending on level.

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!

PgBouncer 1.10.0 is out. The main change is improved support for TLS 1.3. See

https://pgbouncer.github.io/2019/07/pgbouncer-1-10-0

for more information, the detailed changelog, and download links.

PgBouncer is a lightweight connection pooler for PostgreSQL.