PostreSQL.org

PGConf.ASIA 2018 will be held on December 10th to 12th in Tokyo. Join us to meet other users and developers from around the world at the home of the oldest and largest user group; Japan.

The schedule has now been announced!
Including the keynote speeches, a total of 23 sessions will be held.
Full schedule and details of the talks are available online. More details will come soon.

• Day 1
• Day 2

In addition to that, we'll hold the following events.

• Pre-user conference (10th): Its official language is Japanese
• Developer unconference (10th): Its official language is English
• Lightning talks (12th): It'll be held at the end of Day 2
• Official party (12th): It'll be held at the end of Day 2 at the restaurant near the venue

Details of the conference:

• You can buy tickets here
• You can get information about the Venue, Hotels, and Visa here
• Special thanks to our Sponsors!

See you in Tokyo! :)

PGConf.ASIA 2018 Steering Committee https://www.pgconf.asia/EN/2018/

The PostgreSQL Global Development Group has released an update to all supported versions of our database system, including 11.1, 10.6, 9.6.11, 9.5.15, 9.4.20, and 9.3.25. This release fixes one security issue as well as bugs reported over the last three months.

All users using the affected versions of PostgreSQL should update as soon as possible. Please see the notes on "Updating" below for any post-update steps that may be required if you are using pg_stat_statements in your installation.

This update is also the final release for PostgreSQL 9.3, which is now end-of-life and will no longer receive any bug or security fixes. If your environment still uses PostgreSQL 9.3, please make plans to update to a community supported version as soon as possible. Please see our versioning policy for more information.

Security Issues

One security vulnerability has been closed by this release:

• CVE-2018-16850: SQL injection in pg_upgrade and pg_dump, via CREATE TRIGGER ... REFERENCING.

Versions Affected: 10, 11

Using a purpose-crafted trigger definition, an attacker can run arbitrary SQL statements with superuser privileges when a superuser runs pg_upgrade on the database or during a pg_dump dump/restore cycle. This attack requires a CREATE privilege on some non-temporary schema or a TRIGGER privilege on a table. This is exploitable in the default PostgreSQL configuration, where all users have CREATE privilege on public schema.

Bug Fixes and Improvements

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

These releases include fixes that:

• Ensure that automatically created child indexes are created in the same tablespace as the parent partitioned index
• Fix several crashes with triggers
• Fix problems with applying ON COMMIT DELETE ROWS to a partitioned temporary table
• Fix how NULL values are handled when using LEFT JOIN with a parallelized hash join
• Several fixes around using named or defaulted arguments in CALL statements
• Fix for strict aggregate functions (i.e. aggregates that cannot accept NULL inputs) with ORDER BY columns that enforces the strictness check
• Fix with CASE statements where an expression was cast to an array type
• Disable an optimization for updating expression indexes in order to prevent a crash
• Fix a memory leak that occurred on a specific case of using a SP-GiST index
• Fix for pg_verify_checksums incorrectly reporting on files that are not expected to have checksums
• Prevent the PostgreSQL server from starting when wal_level is set to a value that cannot support an existing replication slot
• Ensure that the server will process already-received NOTIFY and SIGTERM interrupts before waiting for client input
• Allow PL/Ruby to work with newer versions of PostgreSQL
• Fix for character-class checks on Windows for Unicode characters above U+FFFF, which affected full-text search as well as contrib/ltree and contrib/pg_trgm
• Fix a case where psql would not report the receipt of a message from a NOTIFY call until after the next command
• Fix build problems on macOS 10.14 (Mojave)
• Several build fixes for the Windows platform

This updates also contains tzdata release 2018g for DST law changes in Chile, Fiji, Morocco, and Russia (Volgograd), plus historical corrections for China, Hawaii, Japan, Macau, and North Korea.

PostgreSQL 9.3 is End-of-Life (EOL)

PostgreSQL 9.3 is now end-of-life and will no longer receive any bug or security fixes. We urge users to start planning an upgrade to a later version of PostgreSQL as soon as possible. Please see our versioning policy for more information.

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.

If your system is using pg_stat_statements and you are running a version of PostgreSQL 10 or PostgreSQL 11, we advise that you execute the following command after upgrading:

ALTER EXTENSION pg_stat_statements UPDATE;

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.

Links

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

TL;DR

• PipelineDB 1.0 is a PostgreSQL extension for high-performance time-series aggregation via continuous SQL queries, offered freely under the Apache 2.0 open-source license
• PipelineDB 1.0 is now available for PostgreSQL 11 and Docker. Visit the getting started docs or download a release package to get started
• PipelineDB enables realtime reporting use cases at scale, where only summary data is needed
• The next release of PipelineDB will include partitioning automation

You can read today's blog post on the PostgreSQL 11 compatibility release for more information.

PGConf.ASIA 2018 will be held on December 10th to 12th in Tokyo. Join us to meet other users and developers from around the world at the home of the oldest and largest user group; Japan.

Now we would like to announce that registration is open! You can get the ticket here .

Ticket types are as follows:

• Event Pass includes Day1/Day2 conference and Official Party
• Conference Pass includes only Day1/Day2 conference
• Official Party includes Official Party ONLY
• Preuser Conference includes Day0 preuser conference (official language is Japanese)
• Unconference includes Day0 developer unconference (official language is English)

NOTE: Day0 is absolutely free of charge but registration is necessary.

All early bird tickets are available till 16 November midnight in Japan time. So please hurry up!

Details of the conference:

• The schedule will be released soon.
• You can get information about the Venue, Hotels, and Visa here
• Special thanks to our Sponsors!

See you in Tokyo!

PGConf.ASIA 2018 Steering Committee https://www.pgconf.asia/EN/2018/

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.1
• 3.7.6
• 3.6.13
• 3.5.17
• 3.4.20

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

Please take a look at release notes.

You can download the source code and RPMs.

Devart has released a new version of dbForge Data Compare for PostgreSQL v.3.1 – a powerful and easy to use tool for table data comparison and synchronization.

Devart, a Czech software provider of database connectivity solutions and tools for database management and development, announced the release of PostgreSQL data diff management tool, dbForge Data Compare for PostgreSQL v3.1, that comes with support for PostgreSQL 10.x and 11.x. The new version provides connectivity support for the latest versions of PostgreSQL which means users can compare, analyze, and deploy PostgreSQL data diffs on the most up-to-date database engines.

dbForge Data Compare for PostgreSQL is a PostgreSQL Data Diff and Sync tool that allows users to review all the differences in tables being compared and execute an automatically generated script to eliminate these differences.

For more information about dbForge Data Compare for PostgreSQL, please visit https://www.devart.com/dbforge/postgresql/datacompare/

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

Oxford, United Kingdom - October 29, 2018

2ndQuadrant is proud to announce the release of pglogical 2.2.1, 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.

pglogical 2.2.1 includes full compatibility with PostgreSQL 11, the newest major release announced by the community on October 18, 2018.

This release presents important enhancements and bug fixes, such as:

• Add pglogical.wait_ for_ subscription _ sync_ complete and pglogical.wait_ for_ table _sync _complete functions
• Allow passing of arguments to pg_ basebackup via pglogical_ create_subscriber
• Update pglReorderBufferCleanSerializedTXNs to match core code
• Improve confusing 'natts mismatch' error
• Improve performance when several table resyncs are done
• Ensure notifications sent by ENABLE REPLICA triggers are sent promptly
• Add pglogical.xact_ commit_timestamp _origin to look up the replication origin associated with a transaction id
• Rewrite worker signalling to address possible loss of messages when multiple signals are delivered, causing issues with sync and apply
• Stop using pglogical.alter_node _drop _interface to drop an interface that is used by a current subscription
• Race condition between pglogical managers trying to register new workers after a crash
• Fix a case where apply crashes are not recovered by the manager
• Fix a memory leak in apply worker trace logic leading to unbounded memory growth in ErrorContext
• Fix uninitialized field causing occasional log messages about "none worker"
• Fix use of the same restore-point name by pglogical_ create _subscriber that could cause the wrong restore-point to be stopped at and an incomplete initial sync

Download and installation instructions are available here.

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

Oxford, United Kingdom - October 25, 2018

2ndQuadrant today announced the release of Postgres-XL 10R1, now available for download here.

Postgres-XL is a massively parallel database built on top of - and very closely compatible with - community PostgreSQL. It supports both Business Intelligence workloads and high-volume transactional read/write workloads, all on the same platform.

Postgres-XL is fully open source. As we begin to move towards a fully parallel, sharded version of core PostgreSQL, many parts of Postgres-XL will be fed into later releases of PostgreSQL.

This major release includes most of the new features added in the latest major PostgreSQL releases such as query parallelism (PostgreSQL 9.6) and declarative partitioning (PostgreSQL 10), now both available in Postgres-XL 10R1. Additionally, Postgres-XL 10R1 includes several significant performance enhancements that have been made to PostgreSQL in the last few years.

This release introduces the following enhancements from major PostgreSQL releases:

PostgreSQL 10

• Declarative table partitioning.
• Improved query parallelism.
• Significant general performance improvements.
• Improved monitoring and control.

PostgreSQL 9.6

• Parallel execution of sequential scans, joins, and aggregates.
• Avoid scanning pages unnecessarily during vacuum freeze operations.
• Substantial performance improvements, especially in the area of scalability on multi-CPU-socket servers.
• Full-text search can now search for phrases (multiple adjacent words).

This new release also includes several bug fixes and enhancements that are Postgres-XL specific. The distributed planner code has been rewritten to utilize advances in the PostgreSQL code.

For a complete list of updates and bug fixes, read full release notes here.

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

Oxford, United Kingdom - October 24, 2018

2ndQuadrant today announced the release of repmgr 4.2 This release includes support for PostgreSQL 11, the newest major release announced by the community last week.

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

The principal new feature of repmgr 4.2 is the ability to "pause" the repmgr daemon (repmgrd) via the repmgr daemon pause and the corresponding repmgr daemon unpause commands. These will temporarily prevent it from taking failover action. This is useful for activities like planned maintenance (e.g. database upgrades or switchovers) which previously required repmgrd to be shut down on all nodes. repmgr standby switchover will automatically pause/unpause repmgrd, simplifying switchover operations.

Additionally, the new repmgr daemon status command is available to provide an overview of repmgrd status on all nodes.

For more details on this functionality, see the detailed documentation.

repmgr 4.2 also provides several usability enhancements:

• Add new parameter shutdown_check_timeout (default: 60 seconds). This provides an explicit timeout for repmgr standby switchover to check that the demotion candidate (current primary) has shut down.

• Add new parameter repmgr_ bindir. This facilitates remote invocation of repmgr when the repmgr binary is located somewhere other than the PostgreSQL binary directory, as it cannot be assumed all package maintainers will install repmgr there. This parameter is optional; if not set (default), repmgr will fall back to pg_ bindir (if set).

• repmgr cluster cleanup now accepts the --node-id option to delete records for only one node.

• When running repmgr cluster matrix and repmgr cluster crosscheck, repmgr will report nodes unreachable via SSH, and emit return code ERR_BAD_SSH.

For a detailed list of all changes, please read the complete release notes here.

Upgrade instructions are available here.

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

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

repmgr is distributed under GPL v3.

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

PipelineDB, which enables high-throughput continuous aggregation of streaming time-series data, released v1.0.0 today as an open-source PostgreSQL extension under the Apache 2.0 license. For more information please read PipelineDB’s v1.0.0 announcement blog post, check out the updated technical docs, and feel free to download PipelineDB v1.0.0 here.

Oxford, United Kingdom - October 23, 2018

2ndQuadrant today announced the release of Barman version 2.5. This release includes support for PostgreSQL 11, the newest major release announced last week by the community.

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.

Barman v2.5 presents the following new features:

• Add support for PostgreSQL 11
• Add check-backup command. This verifies all WAL files required for consistency of a base backup are present in the archive. A new state is added (WAITING_FOR_WALS) after completing a base backup, and it is set to DONE only after all WALL files have been verified.

This release also fixes decoding errors reading external commands output. A complete list of changes and bug fixes is available here.

Download and installation instructions are available here.

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

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

Database .NET v26 is an innovative, powerful and intuitive multiple database management tool. (Full support for PostgreSQL 8/9/10/11)(Free, All-In-One, Portable, Single executable file and Multi-language.)

Major New features from version 24.6 to 26.0:

• Performance improvements for Object Navigator and Data Migration
• PostgreSQL 11 support
• Added SSH: Secure Shell support (PG)
• Added Switching between all databases and a specified database (PG)
• Added support for Foreign and Partitioned tables in PostgreSQL
• Added support for Store Procedures in PostgreSQL 11
• Added Generating 'DELETE+INSERT' statements from results (PG)
• Added Generating script AS UPSERT statement (PG)
• Added support for regular expression for Search Table Data
• Added support for multiple selections (press Ctrl or Shift and click mouse)
• Added Filtering Code Snippets
• Added Showing filter expression on the toolbar in the Edit Mode
• Added Copying Selected Rows to Clipboard
• Added Dragging multiple selections
• Added My Favorite Connections
• Added a shortcut key (Ctrl+T) for Executing query to text
• Improved Graphical User Interface
• Improved Plain Execution Plan and Visual Execution Plan
• Improved Database Diagram
• Improved Generating Scripts
• Improved Form Editor and Form Viewer
• ...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.

Major releases

Pgpool Global Development Group is pleased to announce the availability of Pgpool-II 4.0.0 and pgpoolAdmin 4.0.0.

Pgpool-II 4.0.0 has new features:

• Add SCRAM and Certificate authentication support.
• Detecting "false" primary server of PostgreSQL.
• Improvement of load balancing:
• More load balancing fine control after write queries.
• Load balancing control for specific queries.
• Allow to specify load balance weight ratio for load balance parameters.
• Add last state change timestamp to SHOW POOL NODES.
• Import PostgreSQL 11 SQL parser.
• Logging client messages.
• etc.

Please take a look at release notes.

You can download the source code and RPMs.

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

PostgreSQL 11 provides users with improvements to overall performance of the database system, with specific enhancements associated with very large databases and high computational workloads. Further, PostgreSQL 11 makes significant improvements to the table partitioning system, adds support for stored procedures capable of transaction management, improves query parallelism and adds parallelized data definition capabilities, and introduces just-in-time (JIT) compilation for accelerating the execution of expressions in queries.

"For PostgreSQL 11, our development community focused on adding features that improve PostgreSQL's ability to manage very large databases," said Bruce Momjian, a core team member of the PostgreSQL Global Development Group. "On top of PostgreSQL's proven performance for transactional workloads, PostgreSQL 11 makes it even easier for developers to run big data applications at scale."

PostgreSQL benefits from over 20 years of open source development and has become the preferred open source relational database for developers. The project continues to receive recognition across the industry, and has been featured as the "DBMS of the Year 2017" by DB-Engines and in the SD Times 2018 100.

PostgreSQL 11 is the first major release since PostgreSQL 10 was released on October 5, 2017. The next update release for PostgreSQL 11 containing bug fixes will be PostgreSQL 11.1, and the next major release with new features will be PostgreSQL 12.

Increased Robustness and Performance for Partitioning

PostgreSQL 11 adds the ability to partition data by a hash key, also known as hash partitioning, adding to the current ability to partition data in PostgreSQL by a list of values or by a range. PostgreSQL 11 further improves its data federation abilities with functionality improvements for partitions that use the PostgreSQL foreign data wrapper, postgres_fdw.

To help with managing partitions, PostgreSQL 11 introduces a catch-all default partition for data that does not match a partition key, and the ability to create primary keys, foreign keys, indexes, and triggers on partitioned tables that are passed down to all partitions. PostgreSQL 11 also supports automatically moving rows to the correct partition if the partition key for that row is updated.

PostgreSQL 11 improves upon query performance when reading from partitions by using a new partition elimination strategy. Additionally, PostgreSQL 11 now supports the popular "upsert" feature on partitioned tables, which helps users to simplify application code and reduce network overhead when interacting with their data.

Transactions Supported in Stored Procedures

Developers have been able to create user-defined functions in PostgreSQL for over 20 years, but prior to PostgreSQL 11, these functions were unable to manage their own transactions. PostgreSQL 11 adds SQL procedures that can perform full transaction management within the body of a function, enabling developers to create more advanced server-side applications, such as ones involving incremental bulk data loading.

SQL procedures can be created using the CREATE PROCEDURE command, executed using the CALL command, and are supported by the server-side procedural languages PL/pgSQL, PL/Perl, PL/Python, and PL/Tcl.

Enhanced Capabilities for Query Parallelism

PostgreSQL 11 improves parallel query performance, with performance gains in parallel sequential scans and hash joins along with more efficient scans of partitioned data. PostgreSQL can now execute SELECT queries that use UNION in parallel if the underlying queries are unable to be parallelized.

PostgreSQL 11 adds parallelism to several data definition commands, notably for the creation of B-tree indexes that are generated by executing the standard CREATE INDEX command. Several data definition commands that either create tables or materialized views from queries are also parallel capable now, including the CREATE TABLE .. AS, SELECT INTO, and CREATE MATERIALIZED VIEW.

Just-in-Time (JIT) Compilation for Expressions

PostgreSQL 11 introduces support for Just-In-Time (JIT) compilation to accelerate the execution of certain expressions during query execution. JIT expression compilation for PostgreSQL uses the LLVM project to speed up the execution of expressions in WHERE clauses, target lists, aggregates, projections, and some internal operations.

To take advantage of JIT compilation, you will need to install the LLVM dependencies and enable JIT compilation in either your PostgreSQL settings file by setting jit = on or from your PostgreSQL session by executing SET jit = on.

General User Experience Improvements

The enhancements to the PostgreSQL relational database are not possible without the feedback from an active user community and the hard work by the people who work on PostgreSQL. Below highlights a few of the many features included in PostgreSQL 11 designed to improve the overall user experience:

• Removing the need for ALTER TABLE .. ADD COLUMN .. DEFAULT .. with a not NULL default to rewrite the whole table on execution, which provides a significant performance boost when running this command.
• "Covering indexes," which allows a user to add additional columns to an index using the INCLUDE clause and are helpful for performing index-only scans, especially on data types that are not indexable by B-tree indexes.
• Additional functionality for working with window functions, including allowing RANGE to use PRECEDING/FOLLOWING, GROUPS, and frame exclusion
• The inclusion of the keywords "quit" and "exit" in the PostgreSQL command-line interface to help make it easier to leave the command-line tool

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/11/static/release-11.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. Learn more about PostgreSQL and participate in our community at PostgreSQL.org.

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

Upgrading to PostgreSQL 11 RC 1

To upgrade to PostgreSQL 11 RC 1 from Beta 4 or an earlier version of PostgreSQL 11, 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 11 Beta 4

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

• Fix a crash that occurred with event triggers on partitioned tables
• Ensure the transaction_timestamp function returns an updated timestamp in a stored procedure if it is called after a transaction is committed
• Disallow multiple primary keys to be created on partitions
• Fix for ALTER TABLE .. ATTACH PARTITION

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

Release Schedule

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

For further information please see the Beta Testing page.

Links

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

Following the success of past pan-Asia Postgres events - pgDay Asia and PGConf APAC - we are pleased to announce PGConf APAC 2019, to be held in Singapore from 19th to 21st March, 2019. PGConf APAC is the PostgreSQL conference series for all PostgreSQL enthusiasts in the Asia Pacific region.

pgDay Asia (2016 & 2017) and PGConf APAC 2018 would not have been possible without your awesome talks and we would like to invite speakers from all over the globe to present at the PGConf APAC 2019. We would like to open Call For Paper for PGConf APAC 2019. Some of the topics which can be used for submitting a talk are:

1. Migration projects
2. Performance troubleshooting and tuning
3. noSQL and geo-spatial features of Postgres
4. Unique use-case and customer stories

For some examples you can refer to the papers which were presented at previous years’ events

• 2018
• 2017
• 2016

Of course we are happy to accept paper proposals on any other interesting topics as well.

To submit your proposal for presentation please go to this link (https://pgconfapac.org/events/pgconfapac2019/callforpapers/)[https://pgconfapac.org/events/pgconfapac2019/callforpapers/].

This year we are also introducing trainings. The idea is community helps the community to learn. If you have a great topic in mind which can be covered in 5-6 hours, please go ahead and submit a proposal for that too. Typical topics that can be useful for the audience would be:

• Linux Tuning for PostgreSQL
• Replication
• Backup & Recovery
• Performance Tuning

Of course if you have something different that you have learnt the hard way and want to share with the attendees of PGConf APAC, we would be happy to accept your proposal. The training proposal can be submitted at the same CFP site by choosing 'PostgreSQL Training' as Track.

Important Dates

• Tuesday, March 19th - PostgreSQL Training Day
• Wednesday, March 20th - 1 Day of Postgres Talks
• Thursday, March 21st - 2nd Day of Postgres Talks & Speaker Dinner

Venue

Singapore (More details to be announced)

Call for Presentations

• 2018-10-03: Proposals acceptance begins
• 2018-11-16: Proposals acceptance ends
• 2018-11-30: Authors of accepted proposals contacted

Important Links

• Call for Paper: https://pgconfapac.org/events/pgconfapac2019/callforpapers/
• More details about CFP: https://2019.pgconfapac.org/callforpapers/
• Past Events:
  • 2018
  • 2017
  • 2016
• All other details including team & sponsors: https://2019.pgconfapac.org/

If you need any additional information please contact our team at pgconfapac(at)googlegroups(dot)com

This conference is organized by the PostgreSQL people from Asian communities. If you have any question, feel free to contact us on pgconfapac(at)googlegroups(dot)com.

The PLR team has released 8.3.0.18 which is compatible with PostgreSQL version 11. There are no external changes. The only changes are internal which were required for changes in the internal PostgreSQL procedural language API.

PostgreSQL 11 Beta 4 Released

The PostgreSQL Global Development Group announces that the fourth beta release of PostgreSQL 11 is now available for download. This release contains previews of all features that will be available in the final release of PostgreSQL 11 (though some details could change before a release candidate is made available) as well as bug fixes that were reported during the third beta.

This is likely the last beta release for PostgreSQL 11 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 11 in your database systems to help us eliminate any bugs or other issues that may exist.

Upgrading to PostgreSQL 11 Beta 4

To upgrade to PostgreSQL 11 Beta 4 from Beta 3 or an earlier version of PostgreSQL 11, 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 11 Beta 3

There have been many bug fixes for PostgreSQL 11 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 11. These fixes include:

• JIT compilation is disabled by default. To enable JIT compilation, you must set jit = on in your configuration file or in a session
• Enforce that names for constraints are unique
• Several fixes for stored procedures, including improved hints and documentation around usage
• Several fixes for partitioning, including fixes for runtime partition pruning
• Fix for parallelized CREATE INDEX by disallowing builds on mapped catalog relations
• Fix for REINDEX to prevent unprivileged users from reindexing shared catalogs in certain cases
• Memory-leak fix when multiple calls are made to XMLTABLE in a single query
• Several fixes for pg_verify_checksums
• Several fixes for libpq, including a fix to only look up a hostname when explicitly requested to do so
• Several pg_upgrade fixes, including handling event triggers in extensions correctly
• Several fixes for pg_dump and pg_restore

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 release of PostgreSQL 11. 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 PostgreSQL 11. In all likelihood, this is the final beta release of PostgreSQL 11 before one or more release candidates are made available. For further information please see the Beta Testing page.

Links

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

The PostgreSQL Core team are pleased to announce that following a long consultation process, the project’s Code of Conduct (CoC) has now been finalised and published here.

Please take time to read and understand the CoC, which is intended to ensure that PostgreSQL remains an open and enjoyable project for anyone to join and participate in.

A Code of Conduct Committee has been formed to handle any complaints. This consists of the following volunteers:

• Stacey Haysler (Chair)
• Lætitia Avrot
• Vik Fearing
• Jonathan Katz
• Ilya Kosmodemiansky

We would like to extend our thanks and gratitude to Stacey Haysler for her patience and expertise in helping develop the Code of Conduct, forming the committee and guiding the work to completion.

2ndQuadrant announced today the release of Postgres-XL 10r1beta1, now available for download here.

Postgres-XL is a massively parallel database built on top of - and very closely compatible with - community PostgreSQL and its set of advanced features. It supports both Business Intelligence workloads and high-volume transactional write and read workloads, all on the same platform.

Postgres-XL is fully open source; as we begin to move towards a fully parallel, sharded version of core PostgreSQL, many parts of Postgres-XL will feed directly or indirectly into later releases of PostgreSQL.

Postgres-XL 10R1Beta1 introduces the following enhancements from major PostgreSQL latest releases:

PostgreSQL 10

• Declarative table partitioning
• Improved query parallelism
• Significant general performance improvements
• Improved monitoring and control

PostgreSQL 9.6

• Parallel execution of sequential scans, joins and aggregates
• Avoid scanning pages unnecessarily during vacuum freeze operations
• Substantial performance improvements, especially in the area of scalability on multi-CPU-socket servers
• Full-text search can now search for phrases (multiple adjacent words)

This new release also includes several bug fixes and Postgres-XL specific enhancements. The distributed planner code has been rewritten to utilise advances in the PostgreSQL code.

For a complete list of updates and bug fixes, read full release notes here.

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