aboutsummaryrefslogtreecommitdiffstats
path: root/lib/mnesia
diff options
context:
space:
mode:
Diffstat (limited to 'lib/mnesia')
-rw-r--r--lib/mnesia/doc/src/notes.xml34
1 files changed, 33 insertions, 1 deletions
diff --git a/lib/mnesia/doc/src/notes.xml b/lib/mnesia/doc/src/notes.xml
index f1c362261a..7f50dc049a 100644
--- a/lib/mnesia/doc/src/notes.xml
+++ b/lib/mnesia/doc/src/notes.xml
@@ -38,7 +38,39 @@
thus constitutes one section in this document. The title of each
section is the version number of Mnesia.</p>
- <section><title>Mnesia 4.4.18</title>
+ <section><title>Mnesia 4.4.19</title>
+
+ <section><title>Fixed Bugs and Malfunctions</title>
+ <list>
+ <item>
+ <p>
+ Mnesia could crash if mnesia:add_table_index/2 was
+ invoked before the table was loaded on all nodes.</p>
+ <p>
+ Own Id: OTP-9285 Aux Id: seq11844 </p>
+ </item>
+ <item>
+ <p>
+ Add {majority, boolean()} per-table option.</p>
+ <p>
+ With {majority, true} set for a table, write transactions
+ will abort if they cannot commit to a majority of the
+ nodes that have a copy of the table. Currently, the
+ implementation hooks into the prepare_commit, and forces
+ an asymmetric transaction if the commit set affects any
+ table with the majority flag set. In the commit itself,
+ the transaction will abort if it cannot satisfy the
+ majority requirement for all tables involved in the
+ transaction.(Thanks to Ulf Wiger)</p>
+ <p>
+ Own Id: OTP-9304</p>
+ </item>
+ </list>
+ </section>
+
+</section>
+
+<section><title>Mnesia 4.4.18</title>
<section><title>Fixed Bugs and Malfunctions</title>
<list>