File 0535-Specify-that-mnesia-start-0-is-async.patch of Package erlang

Overview Repositories Revisions Requests Users Attributes Meta

File 0535-Specify-that-mnesia-start-0-is-async.patch of Package erlang

From 35f980b6fd5fa21181f307d49baf1e2ce01a2b7a Mon Sep 17 00:00:00 2001
From: Aleksa Stojanovic <aleksa47@gmail.com>
Date: Mon, 7 Jan 2019 19:18:34 +0100
Subject: [PATCH] Specify that mnesia:start/0 is async

---
 lib/mnesia/doc/src/mnesia.xml | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/lib/mnesia/doc/src/mnesia.xml b/lib/mnesia/doc/src/mnesia.xml
index 94f1af34bf..11b0b8e987 100644
--- a/lib/mnesia/doc/src/mnesia.xml
+++ b/lib/mnesia/doc/src/mnesia.xml
@@ -2077,6 +2077,13 @@ mnesia:create_table(employee,
       <fsummary>Starts a local Mnesia system.</fsummary>
       <desc>
       <marker id="start"></marker>
+        <p>Mnesia startup is asynchronous. The function call
+	        <c>mnesia:start()</c> returns the atom <c>ok</c> and then
+          starts to initialize the different tables. Depending on the
+          size of the database, this can take some time, and the
+          application programmer must wait for the tables that the
+          application needs before they can be used. This is achieved
+          by using the function <c>mnesia:wait_for_tables/2</c>.</p>
         <p>The startup procedure for a set of Mnesia nodes is a
           fairly complicated operation. A Mnesia system consists
           of a set of nodes, with Mnesia started locally on all
-- 
2.16.4

Places

File 0535-Specify-that-mnesia-start-0-is-async.patch of Package erlang

Places