From: Pavan Deolasee Date: Mon, 18 Feb 2019 13:22:51 +0000 (+0530) Subject: Write draft release notes for upcoming XL10r1.1 release X-Git-Tag: XL_10_R1_1~2 X-Git-Url: http://git.postgresql.org/gitweb/static/gitweb.js?a=commitdiff_plain;h=024bce5f5e45cb8e80782a80bdf53ef425254d1d;p=postgres-xl.git Write draft release notes for upcoming XL10r1.1 release --- diff --git a/doc/src/sgml/release-xl-10r1.sgml b/doc/src/sgml/release-xl-10r1.sgml index a16919445f..02e5fda99a 100644 --- a/doc/src/sgml/release-xl-10r1.sgml +++ b/doc/src/sgml/release-xl-10r1.sgml @@ -1,5 +1,137 @@ + + Postgres-XL Release 10r1.1 + + + Release Date + 2019-02-19 + + + This release includes all the bug fixes and security fixes from PostgreSQL +10.6. In addition, there are a few Postgres-XL specific bug fixes in this +release. For information about new features in the Postgres-XL 10r1 major release, see + . + + + Migration to Version Postgres-XL 10r1.1 + + A dump/restore is not required for those running Postgres-XL 10r1. + + + + Changes + + + + Allow RECURSIVE queries to work on function scans. + + + + + + Fix a bug in standby's handling of known XIDs. + + + + + + Fix a problem with pg_rewind where it fails to create temporary objects +on the datanode. + + + + + + Add a new --coordinator-only option to vacuumdb. + + + This makes the facilities provided by ANALYZE (COORDINATOR) available to the +vacuumdb command. + + + + + + Overhaul CREATE BARRIER handling. + + + CREATE BARRIER mechanism now uses higher level locks for synchronization +instead of using LWLocks across network calls. This makes CREATE BARRIER +interruptible and also responsive to timeouts. + + + + + + Fix a bug where certain kinds of joins were not getting pushed down to +the datanodes. + + + When a query involves a 3-way (or N-way) join between two distributed tables and + a replicated table, such joins should be shippable to datanodes as long as the + join between the distributed tables is an equi-join on the distributed column, + with the same distribution property AND the join between the result of the join + on distributed tables and the replicate table is either an INNER JOIN or a LEFT + JOIN where the right side is the replicated table. This fix allows such joins to + be pushed down to the datanodes. + + + + + + Implement additional coordinator/datanode GUCs to control communication between nodes and the +GTM. + + + + + gtm_connect_timeout specifies the timeout in +seconds that a node waits for connecting to the GTM. + + + The default value of the GUC is 60. + + + + + gtm_comm_timeout specifies the timeout in +seconds that a node waits for the response from the GTM. + + + The default value of the GUC is 0 which means the +node will wait forever for the response. User may change value of this +parameter if faced with unpleasant situations where the node infinitely waits +for a response from the GTM. Otherwise this should be left to the default. + + + + + + + Add a new comm_timeout GUC to the GTM proxy. + + + This specifies a timeout in seconds that the proxy waits for response + from the GTM.The default value of the GUC is 0 which means the proxy + will wait forever for the response. User may change value of this parameter in + GTM proxy's configuration file if faced with unpleasant situations where the + proxy infinitely waits for a response from the GTM. Otherwise this should be + left to the default. + + + + + + Fix a bug in handling of multiple unix domain socket directories on the +GTM side. + + + + + + + Postgres-XL Release 10r1