PostreSQL.org

Eymoutiers, France, November 6, 2019

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, Partial Scrambling, Shuffling, Noise Addition and Generalization.

Generalization

The idea of generalization is to replace data with a broader, less accurate value. For instance, instead of saying "Bob is 28 years old", you can say "Bob is between 20 and 30 years old". This is interesting for analytics because the data remains true while avoiding the risk of re-identification.

PostgreSQL can handle generalization very easily with the RANGE data types, a very powerful way to store and manipulate a set of values contained between a lower and an upper bound.

Here's a basic table containing medical data:

SELECT * FROM patient; ssn | firstname | zipcode | birth | disease -------------+-----------+---------+------------+--------------- 253-51-6170 | Alice | 47012 | 1989-12-29 | Heart Disease 091-20-0543 | Bob | 42678 | 1979-03-22 | Allergy 565-94-1926 | Caroline | 42678 | 1971-07-22 | Heart Disease 510-56-7882 | Eleanor | 47909 | 1989-12-15 | Acne

We want the anonymized data to remain true because it will be used for statistics. We can build a view upon this table to remove useless columns and generalize the indirect identifiers (zipcode and birthday):

CREATE MATERIALIZED VIEW generalized_patient AS SELECT 'REDACTED'::TEXT AS firstname, anon.generalize_int4range(zipcode,1000) AS zipcode, anon.generalize_daterange(birth,'decade') AS birth, disease FROM patient;

This will give us a less accurate view of the data:

SELECT * FROM generalized_patient; firstname | zipcode | birth | disease -----------+---------------+-------------------------+--------------- REDACTED | [47000,48000) | [1980-01-01,1990-01-01) | Heart Disease REDACTED | [42000,43000) | [1970-01-01,1980-01-01) | Allergy REDACTED | [42000,43000) | [1970-01-01,1980-01-01) | Heart Disease REDACTED | [47000,48000) | [1980-01-01,1990-01-01) | Acne k-anonymity

k-anonymity is an industry-standard term used to describe a property of an anonymized dataset. The k-anonymity principle states that within a given dataset, any anonymized individual cannot be distinguished from at least k-1 other individuals. In other words, k-anonymity might be described as a "hiding in the crowd" guarantee. A low value of k indicates there's a risk of re-identification using linkage with other data sources.

You can evaluate the k-anonymity factor of a table in 2 steps :

1/ First defined the columns that are [indirect idenfiers] ( also known as "quasi identifers") like this:

SECURITY LABEL FOR anon ON COLUMN generalized_patient.zipcode IS 'INDIRECT IDENTIFIER'; SECURITY LABEL FOR anon ON COLUMN generalized_patient.birth IS 'INDIRECT IDENTIFIER';

2/ Once the indirect identifiers are declared :

SELECT anon.k_anonymity('generalized_patient')

In the example above, the k-anonymity factor of the generalized_patient materialized view is 2.

Lorem Ipsum

For TEXT and VARCHAR columns, you can now use the classic Lorem Ipsum generator:

• anon.lorem_ipsum() returns 5 paragraphs
• anon.lorem_ipsum(2) returns 2 paragraphs
• anon.lorem_ipsum( paragraphs := 4 ) returns 4 paragraphs
• anon.lorem_ipsum( words := 20 ) returns 20 words
• anon.lorem_ipsum( characters := 7 ) returns 7 characters

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 system, 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 and ideas from Travis Miller, Jan Birk 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 here:

https://gitlab.com/dalibo/postgresql_anonymizer/issues?label_name%5B%5D=Junior+Jobs

PG Down Under 2019 is the annual PostgreSQL conference in Australia which provides a unique opportunity for PostgreSQL Enthusiasts to meet, learn, grow relationships and generally get to know others that use PostgreSQL professionally or just for fun!

There are only four days left to take advantage of #PGDU 2019 PostgreSQL conference as ,we are closing our early bird registrations on 4th Nov, 2019 COB. Hurry up and confirm your registration today. Be sure to snag your tickets before the prices go up by 20% .

PGDU,we have lined up great speaker to present great talks for you from all over the world.

Register today: https://pgdu.org/events/pgdu2019/register/ Event Date: November 15, 2019
SCHEDULE: https://pgdu.org/events/pgdu2019/schedule/

We are pleased to announce the new major version of SQL Manager for PostgreSQL - a high performance tool for PostgreSQL database administration and development. You can download the newest version from the download page.

What's new in SQL Manager for PostgreSQL 6.0?

1. Support of dark visual scheme added.
2. The new look with updated icons.
3. Added support for PostgreSQL 12.0.
4. Support of Unicode added for object names.
5. Improved support of high-DPI monitors and large-scale fonts.
6. Editor tabs can be now highlighted with color specified for the database.
7. Support for server aliases implemented.
8. JSON tab added for viewing data.
9. Description support added for tablespaces.
10. "Refresh concurrently" command added for materialized views.
11. Trailing spaces are not automatically trimmed for CHAR fields now.
12. Fixes and improvements of auto completion feature in query editor.
13. Custom formatting can now be applied to timestamptz data.
14. Many other bug-fixes.
15. Other improvements of interface and usability.

We hope you’ll enjoy working with our software.

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.7
• 3.7.12
• 3.6.19
• 3.5.23
• 3.4.26

Please note that 3.4.26 is the last release of 3.4 series because 5 years has passed since 3.4 was out (2014/11).

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.

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.

Major releases

Pgpool Global Development Group is pleased to announce the availability of Pgpool-II 4.1.0.

Pgpool-II 4.1.0 has new features:

• Statement level load balancing.
• Auto failback.
• Enhance performance in number of areas.
• Shared relation cache allows to reuse relation cache among sessions to reduce internal queries against PostgreSQL system catalogs.
• Have separate SQL parser for DML statements to eliminate unnecessary parsing effort.
• Load balancing control for specific queries.
• Reduce Internal Queries against System Catalogs.
• Import PostgreSQL 12 SQL parser.
• etc.

Please take a look at release notes.

You can download the source code and RPMs.

PgDay San Francisco (PgDay SF) is a 1-day 1-track PostgreSQL conference to be held in San Francisco on January 21, 2020. Registration & CFP are open. Call for Sponsors is coming very soon. There is something special about spending a full day with Postgres developers, users, customers, community members, and experts—where everyone is participating in the same conversation.

https://2020.pgdaysf.org

pgMustard

pgMustard is a tool that gives performance advice based on PostgreSQL query plans (EXPLAIN output). We’re excited to announce version 2!

Improvements since v1

• Tips are far more selectively shown, based on their time-saving potential
• More types of problem can be identified, including table bloat, index inefficiency, and lossy bitmap scans
• Streamlined the UI to make it quicker and easier to diagnose issues
• Lots of smaller fixes and improvements

Requirements

• JSON format query plans
• PostgreSQL 9.6 and newer
• English language only
• Web application, no installation or database access required
• GitHub or Google account, for authentication

Free trial

pgMustard is commercial software and has a free trial: https://www.pgmustard.com/

If you have any slow queries to speed up, we’d love to hear how you get on.

PG Down Under 2019 is the annual PostgreSQL conference in Australia which provides a unique opportunity for PostgreSQL Enthusiasts to meet, learn, grow relationships and generally get to know others that use PostgreSQL professionally or just for fun!

Location: Fishburners Level 2, 11 York Street Sydney NSW AUSTRALIA

Date: November 15, 2019

REGISTRATION: https://pgdu.org/events/pgdu2019/register/

SCHEDULE: https://pgdu.org/events/pgdu2019/schedule/

We are pleased to announce our special Keynote Speaker: Stephen Frost

Stephen will be sharing insights on "PostgreSQL v12 and Beyond"

Stephen is a PostgreSQL Committer, Major Contributor, and involved in many aspects of the PostgreSQL Community from the technology to running Meetups and working with various NPOs around the world to promote PostgreSQL.

New milestone PostgresDAC release is out! Now with PostgreSQL 12 and RAD Studio 10.3.2 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:

• [!] v12 client libraries added
• [!] v12 dump & restore libraries (pg_dump.dll, pg_restore.dll) added
• [!] RAD Studio 10.3.2 (Delphi and C++ Builder) support introduced

Download

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

We are very glad to announce the 3.2.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 new version supports from 9.5 to v12 PostgreSQL versions.

It brings new capabilities in configuring tables groups, with a set of functions that dynamically add or remove tables or sequences to/from groups. The sql script generation feature has also been improved.

This version also includes 6 bug fixes.

The Emaj_web web client has been enhanced to take benefit from these changes.

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 !

Today, the PostgreSQL Community Code of Conduct Committee welcomes two new members:

• Carole Arnaud is an executive board member of Dalibo and team manager. She lives in Nantes, France. She was part of the PGDay France committee from 2015 to 2018 and has been co-organizer of pgDay Paris since 2018.
• Umair Shahid heads Marketing & Products for 2ndQuadrant and is based in Islamabad, Pakistan. He serves as a member of PgUS User Group committee, along with being the organizer for Islamabad and Dubai PostgreSQL Users' Groups. As part of his day job, he organizes the annual PostgresLondon event.

Carole and Umair are taking the place of Laetitia Avrot and Vik Fearing, who served on the initial Committee.

We appreciate Laetitia's and Vik's work on the Committee for the past year, and look forward to working with Carole and Umair.

The current members continuing into the new term are:

• Stacey Haysler (Chair)is the CFO and COO of PostgreSQL Experts, Inc., in Alameda, California. She is a PostgreSQL Global Development Group Contributor, and is also a principal organizer of the San Francisco PostgreSQL Users’ Group and PgDay San Francisco.
• Ilya Kosmodemiansky is a CEO and co-founder at Data Egret, lives in Saarbruecken, Germany. He is a co-organizer of usergroups and meetups (PostgreSQL User group Frankfurt-am-Main, DevOpsSaar meetup) and is part of the organization team of several conferences (PGConf.EU, FOSDEM PGDay, PGDay.Russia). He is also a member of the Sponsorship Committee of PostgreSQL Project.
• Jonathan S. Katz is the Director of Cloud Engineering & Growth at Crunchy Data, and lives in New York. He is a PostgreSQL Global Development Group Major Contributor focused on advocacy, the website, and releases, and also serves on the board of the United States PostgreSQL Association.

The full list of Committee members is always available at: https://www.postgresql.org/about/policies/coc_committee/

PgBouncer 1.12.0 is out. This release contains a variety of minor enhancements and fixes.

This release also contains some fixes to the new SCRAM support in PgBouncer 1.11.0, improving interoperability with newer PostgreSQL versions, so users of SCRAM are particularly advised to upgrade.

See

https://www.pgbouncer.org/2019/10/pgbouncer-1-12-0

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

PgBouncer is a lightweight connection pooler for PostgreSQL.

Yohz Software has just released DB Doc 7.0, the PostgreSQL schema documentation tool, and is available for immediate download.

Changes in this version:

• Added support for PostgreSQL 12.
• Better compatibility on systems using high-dpi displays.

DB Doc benefits:

• Document a PostgreSQL database in 5 simple steps
• Create documentation in HTML, XML, PDF, CHM, and MS Word formats. You can view the samples here.
• Eliminate tedious and time-consuming manual documentation tasks
• Satisfy audit requirements by keeping complete and timely documentation
• View inter-object and inter-database dependencies in your documents
• View statistical data like the largest tables and indexes in each database
• Document layouts are fully customizable to suit your requirements
• Keep teams up to date by distributing timely and accurate documentation
• Supports PostgreSQL 8.3 and newer, without the need for any additional database drivers.
• Runs on Windows XP to Windows 10

For more details about DB Doc, please visit the product page. DB Doc-related technical blogs are available here. A discount is available for a limited time using the coupon code POSTGRESQL12.

The PostgreSQL Global Development Group today announced the release of PostgreSQL 12, the latest version of the world's most advanced open source database.

PostgreSQL 12 enhancements include notable improvements to query performance, particularly over larger data sets, and overall space utilization. This release provides application developers with new capabilities such as SQL/JSON path expression support, optimizations for how common table expression (WITH) queries are executed, and generated columns. The PostgreSQL community continues to support the extensibility and robustness of PostgreSQL, with further additions to internationalization, authentication, and providing easier ways to administrate PostgreSQL. This release also introduces the pluggable table storage interface, which allows developers to create their own methods for storing data.

"The development community behind PostgreSQL contributed features for PostgreSQL 12 that offer performance and space management gains that our users can achieve with minimal effort, as well as improvements in enterprise authentication, administration functionality, and SQL/JSON support." said Dave Page, a core team member of the PostgreSQL Global Development Group. "This release continues the trend of making it easier to manage database workloads large and small while building on PostgreSQL's reputation of flexibility, reliability and stability in production environments."

PostgreSQL benefits from over 20 years of open source development and has become the preferred open source relational database for organizations of all sizes. The project continues to receive recognition across the industry, including being featured for the second year in a row as the "DBMS of the Year" in 2018 by DB-Engines and receiving the "Lifetime Achievement" open source award at OSCON 2019.

Overall Performance Improvements

PostgreSQL 12 provides significant performance and maintenance enhancements to its indexing system and to partitioning.

B-tree Indexes, the standard type of indexing in PostgreSQL, have been optimized in PostgreSQL 12 to better handle workloads where the indexes are frequently modified. Using a fair use implementation of the TPC-C benchmark, PostgreSQL 12 demonstrated on average a 40% reduction in space utilization and an overall gain in query performance.

Queries on partitioned tables have also seen demonstrable improvements, particularly for tables with thousands of partitions that only need to retrieve data from a limited subset. PostgreSQL 12 also improves the performance of adding data to partitioned tables with INSERT and COPY, and includes the ability to attach a new partition to a table without blocking queries.

There are additional enhancements to indexing in PostgreSQL 12 that affect overall performance, including lower overhead in write-ahead log generation for the GiST, GIN, and SP-GiST index types, the ability to create covering indexes (the INCLUDE clause) on GiST indexes, the ability to perform K-nearest neighbor queries with the distance operator (<->) using SP-GiST indexes, and CREATE STATISTICS now supporting most-common value (MCV) statistics to help generate better query plans when using columns that are nonuniformly distributed.

Just-in-time (JIT) compilation using LLVM, introduced in PostgreSQL 11, is now enabled by default. JIT compilation can provide performance benefits to the execution of expressions in WHERE clauses, target lists, aggregates, and some internal operations, and is available if your PostgreSQL installation is compiled or packaged with LLVM.

Enhancements to SQL Conformance & Functionality

PostgreSQL is known for its conformance to the SQL standard - one reason why it was renamed from "POSTGRES" to "PostgreSQL" - and PostgreSQL 12 adds several features to continue its implementation of the SQL standard with enhanced functionality.

PostgreSQL 12 introduces the ability to run queries over JSON documents using JSON path expressions defined in the SQL/JSON standard. Such queries may utilize the existing indexing mechanisms for documents stored in the JSONB format to efficiently retrieve data.

Common table expressions, also known as WITH queries, can now be automatically inlined by PostgreSQL 12, which in turn can help increase the performance of many existing queries. In this release, a WITH query can be inlined if it is not recursive, does not have any side-effects, and is only referenced once in a later part of a query.

PostgreSQL 12 introduces "generated columns." Defined in the SQL standard, this type of column computes its value from the contents of other columns in the same table. In this version, PostgreSQL supports "stored generated columns," where the computed value is stored on the disk.

Internationalization

PostgreSQL 12 extends its support of ICU collations by allowing users to define "nondeterministic collations" that can, for example, allow case-insensitive or accent-insensitive comparisons.

Authentication

PostgreSQL expands on its robust authentication method support with several enhancements that provide additional security and functionality. This release introduces both client and server-side encryption for authentication over GSSAPI interfaces, as well as the ability for PostgreSQL to discover LDAP servers if PostgreSQL is compiled with OpenLDAP.

Additionally, PostgreSQL 12 now supports a form of multi-factor authentication. A PostgreSQL server can now require an authenticating client to provide a valid SSL certificate with their username using the clientcert=verify-full option and combine this with the requirement of a separate authentication method (e.g. scram-sha-256).

Administration

PostgreSQL 12 introduces the ability to rebuild indexes without blocking writes to an index via the REINDEX CONCURRENTLY command, allowing users to avoid downtime scenarios for lengthy index rebuilds.

Additionally, PostgreSQL 12 can now enable or disable page checksums in an offline cluster using the pg_checksums command. Previously page checksums, a feature to help verify the integrity of data stored to disk, could only be enabled at the time a PostgreSQL cluster was initialized with initdb.

For a full list of features included in this release, please read the release notes, which can be found at: https://www.postgresql.org/docs/12/release-12.html

About PostgreSQL

PostgreSQL is the world's most advanced open source database, with a global community of thousands of users, contributors, companies and organizations. The PostgreSQL Project builds on over 30 years of engineering, starting at the University of California, Berkeley, and has continued with an unmatched pace of development. PostgreSQL's mature feature set not only matches top proprietary database systems, but exceeds them in advanced database features, extensibility, security, and stability.

Press Release Translations

• Chinese
• French
• German
• Hebrew
• Japanese
• Portuguese
• Russian
• Spanish

Links

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

PgDU 2019, being held in lovely Sydney, has opened registration with Early Bird tickets available now!!!

PostgreSQL Down Under Incorporated, known as PGDU, is a not for profit association. Our purpose is to support the growth and education of PostgreSQL, The World's Most Advanced Open Source Database. Come join us to learn, teach and have fun! Our PgDU conference will be held at Fishburners in Sydney, NSW on November the 15th.

You can register here. Early Bird ticket sales are available until the end of October, Don't wait!!

Call for Papers is closing very soon (5th of October), so if you would like to submit a talk, please submit it here.

Sponsors

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

Fujitsu

2ndQuadrant

Enterprise DB

Sponsorship opportunities are still available! Please see our prospectus if you would like to contribute to PgDU and help strengthen the Australian and New Zealand PostgreSQL community.

The PostgreSQL Global Development Group announces that the first release candidate of PostgreSQL 12 is now available for download. As a release candidate, PostgreSQL 12 RC 1 should be identical to the initial release of PostgreSQL 12, though some more fixes may be applied prior to the general availability of PostgreSQL 12.

The planned date for the general availability of PostgreSQL 12 is October 3, 2019. Please see the "Release Schedule" section for more details.

Upgrading to PostgreSQL 12 RC 1

To upgrade to PostgreSQL 12 RC 1 from Beta 4 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 4

There have been many bug fixes for PostgreSQL 12 reported during the Beta 4 period and applied to this release candidate. These include:

• Add additional "leakproof" markings to certain string functions to better support nondeterministic collations. This can positively impact the performance of some query plans
• Removal of the ECPG DECLARE STATEMENT functionality
• The ecpglib major version change was reverted
• Fix handling of nondeterministic collations with pattern_ops opclasses

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

Release Schedule

This is the first release candidate for PostgreSQL 12. Unless an issue is discovered that warrants a delay or to produce an additional release candidate, PostgreSQL 12 should be made generally available on October 3, 2019.

For further information please see the Beta Testing page.

Links

• Download
• Beta Testing Information
• PostgreSQL 12 RC Release Notes
• PostgreSQL 12 Open Issues
• Submit a Bug
• Follow @postgresql on Twitter

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.