From: Craig Ringer Date: Tue, 26 May 2015 12:18:37 +0000 (+0800) Subject: Release notes for 0.9.1 X-Git-Url: http://git.postgresql.org/gitweb/static/session/%7B%7Bsession.id%7D%7D-%7B%7Bsession.title%7Cslugify%7D%7D?a=commitdiff_plain;h=02a0d91596c85a5906e88b4742c4db9980f08e2a;p=2ndquadrant_bdr.git Release notes for 0.9.1 --- diff --git a/doc/appendix-releasenotes.sgml b/doc/appendix-releasenotes.sgml index bc0c0bb7f3..39409ae0e3 100644 --- a/doc/appendix-releasenotes.sgml +++ b/doc/appendix-releasenotes.sgml @@ -15,6 +15,56 @@ See also: . + + Release 0.9.1 + + + Version 0.9.1 is a maintenance release focused on stability + and performance. + + + + Significant improvements to &bdr; and &udr; in this release include: + + Fix PK detection on inherited tables (BDR) + Fix bdr.bdr_replication_identifier table definition (UDR) + Don't acquire table locks in command filter (BDR/UDR) + Rename 'bdr' reserved db to 'bdr_supervisordb', prevent users from connecting, and protect against drop (BDR/UDR, #60) + Bug fixes in bdr_init_copy handling of connection strings (BDR/UDR, #61) + Fixes for UNLOGGED tables in the command filter (BDR/UDR, #44) + Permit fast shutdown when replication is paused (BDR/UDR, #58) + Introduce to help prevent unintended global DDL locks + Remove slots when parting a node (BDR, #73) + bdr.table_set_replication_sets no longer requires permit_unsafe_ddl_commands (UDR, #67) + Improve sequencer locking and pgstat reporting (BDR/UDR) + Add information function + + Where available a github bug number follows the release entry. Additional + details are available from the changelog in git. + + + + Two changes add minor new functionality: + + + + As of 0.9.1 it is now possible for sessions to SET + bdr.permit_ddl_locking = false to cause commands that would + require the global DDL lock to be acquired to instead fail with an ERROR. + Administrators may choose to set this in postgresql.conf + then have sessions that intend to do DDL override it. See and for more information. + + + + The new information function + can be called on a node to determine whether replay from peer nodes is + paused on that node. + + + + Release 0.9.0 diff --git a/doc/manual-functions.sgml b/doc/manual-functions.sgml index b4f94bcb40..0f24bcc1a3 100644 --- a/doc/manual-functions.sgml +++ b/doc/manual-functions.sgml @@ -172,7 +172,7 @@ - + &bdr;/&udr;