dhis2-devs team mailing list archive

[noreply@xxxxxxxxxxxxx]

------------------------------------------------------------
revno: 865
committer: Lars Helge Øverland <larshelge@xxxxxxxxx>
branch nick: dhis2-docbook-docs
timestamp: Mon 2013-11-18 18:08:49 +0100
message:
  Minor
modified:
  src/docbkx/en/dhis2_implementation_guide_installation.xml


--
lp:~dhis2-documenters/dhis2/dhis2-docbook-docs
https://code.launchpad.net/~dhis2-documenters/dhis2/dhis2-docbook-docs

Your team DHIS 2 developers is subscribed to branch lp:~dhis2-documenters/dhis2/dhis2-docbook-docs.
To unsubscribe from this branch go to https://code.launchpad.net/~dhis2-documenters/dhis2/dhis2-docbook-docs/+edit-subscription

=== modified file 'src/docbkx/en/dhis2_implementation_guide_installation.xml'
--- src/docbkx/en/dhis2_implementation_guide_installation.xml	2013-11-18 15:55:14 +0000
+++ src/docbkx/en/dhis2_implementation_guide_installation.xml	2013-11-18 17:08:49 +0000
@@ -94,10 +94,10 @@
       <para>Determines the amount of memory used for internal sort and hash operations. This setting
       is per connection, per query so a lot of memory may be consumed if raising this too high.
       Setting this value correctly is essential for DHIS 2 aggregation performance.</para>
-      <para><screen>maintenance_work_mem = 256MB</screen></para>
+      <para><screen>maintenance_work_mem = 512MB</screen></para>
       <para>Determines the amount of memory PostgreSQL can use for maintenance operations such as
-      creating indexes, running vacuum, adding foreign keys. Incresing this value might improve
-      performance of index creation during the analytics and data mart generation processes.</para>
+        creating indexes, running vacuum, adding foreign keys. Incresing this value might improve
+        performance of index creation during the analytics generation processes.</para>
       <para><screen>effective_cache_size = 8000MB</screen></para>
       <para>An estimate of how much memory is available for disk caching by the operating system (not
       an allocation) and is used by PostgreSQL to determine whether a query plan will fit into