From: Pavan Deolasee Date: Thu, 13 Sep 2018 10:12:14 +0000 (+0530) Subject: Write draft release notes for Postgres-XL 10r1beta1 X-Git-Tag: XL_10_R1BETA1~7 X-Git-Url: http://git.postgresql.org/gitweb/static/gitweb.js?a=commitdiff_plain;h=301a657cd7fcfe57b78deb623140580ef77459da;p=postgres-xl.git Write draft release notes for Postgres-XL 10r1beta1 --- diff --git a/doc/src/sgml/filelist.sgml b/doc/src/sgml/filelist.sgml index 37bddc7f4e..d45a2a1eb9 100644 --- a/doc/src/sgml/filelist.sgml +++ b/doc/src/sgml/filelist.sgml @@ -172,6 +172,7 @@ + diff --git a/doc/src/sgml/release-xl-10r1.sgml b/doc/src/sgml/release-xl-10r1.sgml new file mode 100644 index 0000000000..a14eccd4b8 --- /dev/null +++ b/doc/src/sgml/release-xl-10r1.sgml @@ -0,0 +1,447 @@ + + + + Postgres-XL Release 10r1beta1 + + + Release Date + 2018-09-14 + Current as of 2016-09-14 + + + + Overview + + This major release of Postgres-XL comes +almost 2 years after Postgres-XL 9.5 was released, +which was based on +PostgreSQL 9.5. This release includes most of the +new features added in PostgreSQL 9.6 and 10 +releases. This also includes almost all significant performance enhancements +that were made to PostgreSQL in the last few years. + + + + Apart from this, a lot of work has gone into fixing outstanding bugs, +improving stability of the product and significantly improving performance for OLTP +workloads. The following sections describe the major enhancements in +PostgreSQL that are now available in +Postgres-XL. A short list of features that are +currently not supported or have limited support is also mentioned in +. + + + + + Migration to Postgres-XL 10r1beta1 + + Migration to Postgres-XL 10r1beta1 from PostgreSQL 10 + + A dump/restore using + is required for those wishing to migrate + data from PostgreSQL 10 release. We don't currently support , as a mechanism to upgrade from PostgreSQL 10. + + + + + + + Migration to Postgres-XL 10r1beta1 from Postgres-XL 9.5r1.x + + Version 10r1beta1 contains a number of changes that may affect compatibility + with previous releases. Since Postgres-XL 10r1beta1 release includes all changes +from PostgreSQL 9.6 and PostgreSQL 10 releases, it is +recommended that you review respective release notes of those releases to find +the exact incompatibilities. + + + + + + Major Enhancements in Postgres-XL 10r1beta1 + + Postgres-XL 10r1beta1 is the first major release +after Postgres-XL 9.5r1 release. So this release +contains most of the major enhancements that went into +PostgreSQL releases 9.6 and 10. This is a very +short list of such enhancements, but all other enhancements also apply, unless +otherwise stated. + + + Major Enhancements from PostgreSQL 10 + + Declarative table partitioning + Improved query parallelism + Significant general performance improvements + Improved monitoring and control + + + + Major Enhancements from 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) + + + + + + Changes + + + Below you will find a detailed account of the changes between + Postgres-XL 10r1beta1 and the previous major + release. + + + + Performance + + + + Allow minimum value of pgxl_remote_fetch_size to zero + + + This is an experimental work. By setting pgxl_remote_fetch_size to 0, user can + fetch all rows at once from the remote side (instead of fetching a small number + at a time, thus giving the node to produce more rows as the previous set is + consumed). While fetching all rows at once is not very useful, it allows us to + circumvent PostgreSQL's limitation of not supporting parallel queries unless a + Portal is run once and to the end. + + + + + Automatically trigger ANALYZE (COORDINATOR) on remote coordinators + + + When a table is manually or automcatically analyzed, the coordiantor + will an ANALYZE (COORDINATOR) command to all other coordinators for them to + update their planner stats. This ensures that the planner stats remain up to date on all + coordinators in the cluster. The feature works when a table is analyzed + outside a transaction block. + + + + + Collect index statistics during ANALYZE on coordinator. + + + + + Randomize the choice of the initial ROUNDROBIN node. + + + + + + Additional Features + + + + pgxc_ctl is now a built-in command and gets +automatically compiled and installed along with other binaries. + + + + + Enable Hot Standby on the replicas. + + + + + Add support for MODULO distribution on BIGINT. + + + + + Support an additional syntax ANALYZE (COORDINATOR) to allow users to rebuild + coordinator side statistics without running ANALYZE again on the datanodes. + + + + + Support GROUPING SETS, ROLLUP and CUBE. + + + + + + Improvements to pgxc_ctl + + + + pgxc_ctl is now a built-in command and gets +automatically compiled and installed along with other binaries. + + + + + + Misc Improvements + + + + pgxc_ctl is now a built-in command and gets +automatically compiled and installed along with other binaries. + + + + + + + Important Bug Fixes + + + + Make improvements to cluster monitor process and global state +reporting. + + + + + Correctly select the GTM proxy for a new node being added. + + + + + Fixes related to handling of schema qualification of temporary tables on remote nodes. + + + + + Fix handling of REFRESH MATERIALIZED VIEW CONCURRENTLY. + + + + + Improve locking semantics in GTM and GTM Proxy. + + + + + Ensure pooler process follows consistent model for SIGQUIT handling. + + + + + Fix broken implementation of recovery to barrier. + + + + + Track clearly whether to run a remote transaction in autocommit or a block. + + + + + Disable FQS for cursors defined with SCROLL. + + + + + Ensure that database objects are created consistently. + + + + We now create views/materialised views on all nodes, unless they are temporary + objects in which case they are created only on the local coordinator and the + datanodes. Similarly, temporary sequences are created on the local coordinator + and the datanodes. + + + + + Prevent dropping distribution keys for MODULO. + + + + + Use thread-specific storage for computing a snapshot. + + + + + Add a user configurable parameter to control the number of rows fetched from + the remote side during RemoteSubplan execution. Switch connections after processing pgxl_remote_fetch_size rows. + + + + + Allow COPY (INSERT RETURNING). + + + + + Handle temp sequences so that duplicate values are not produced. + + + + + Ensure that the config parameters specified in the gtmPxyExtraConfig file take + precendence over the defaults. + + + + + Handle sequence's transactional behaviour on GTM. + + + + + Handle multi-command queries correctly inside SQL as well as plpgsql functions. + + + + + Do not silently skip FK constraints if loose_constraints are ON. + + + + + Ensure that the statistics about all-visible pages in fetched from remote + datanodes and updated at the coordinator for better planning. + + + + + + Known Limitation + + While Postgres-XL strives hard to stay compatible +with PostgreSQL so that applications running on +PostgreSQL can be easily ported to +Postgres-XL, there are certain known limitations of +the product. Many of these can be addressed as and when sufficient development +funding and resources become available. + + + + Distributed deadlock detection is not supported yet. Deadlock detection exists + on each node, just not across nodes. + + + + + Materialised views are currently maintained only on the coordinator. + + + + + EXCLUSION CONSTRAINTS are enforced when both rows map to the same datanode. + + + + + User defined functions have several limitations. + + + + + There are restrictions on complex UPDATE/DELETE queries and updating +distribution column values. + + + + + TRIGGERs are not supported. + + + + + EVENT TRIGGERs are not supported. + + + + + SERIALIZABLE TRANSACTIONs are not supported. + + + + + CREATE INDEX CONCURRENTLY is not supported. + + + + + SAVEPOINTs are not supported. + + + + + Large objects are not supported. + + + + + Recursive queries work only in certain conditions. + + + + + + + + + Foreign Data Wrappers are not supported. + + + + + INSENSITIVE/SCROLL/WITH HOLD cursors are not supported. + + + + + LISTEN/NOTIFY is not supported. + + + + + Remote Subplan nodes are marked parallel unsafe. This implies that + parallel workers can only be used for bottom most Remote Subplan node(s) in a + plan tree. + + + + + CREATE PUBLICATION/SUBSCRIBER is not supported. + + + + + All partitions of a partitioned table must have consistent column ordering +and column positioning. + + + + + + + Contributing to Postgres-XL + + Contributions to Postgres-XL are welcome. The +code will be accepted under the same open source license that governs this +released version of Postgres-XL. The authors of the +patches will be credited appropriately in the release notes of the future +releases. + + + + Credits + + Postgres-XL has been evolving over many years, +originating with the GridSQL +project and Postgres-XC, later combined as TransLattice Storm (StormDB). +TransLattice open sourced the project, resulting in Postgres-XL 9.2. More +recently, the EU-funded Big Data project AXLE funded the main work to bring the +code up to date as Postgres-XL 9.5, allowing +Postgres-XL to take advantage of the +rapidly increasing BI features plugged into the core of +PostgreSQL. + + + diff --git a/doc/src/sgml/release.sgml b/doc/src/sgml/release.sgml index 7e3e2c5c44..14dde15da3 100644 --- a/doc/src/sgml/release.sgml +++ b/doc/src/sgml/release.sgml @@ -74,6 +74,7 @@ For new features, add links to the documentation sections. The reason for splitting the release notes this way is so that appropriate subsets can easily be copied into back branches. --> +&release-xl-10r1; &release-10; &release-9.6; &release-xl-9.5r1;