[postgis-tickets] r16890 - Formatting

Paul Ramsey pramsey at cleverelephant.ca
Fri Oct 12 02:15:03 PDT 2018


Author: pramsey
Date: 2018-10-12 14:15:03 -0700 (Fri, 12 Oct 2018)
New Revision: 16890

Modified:
   trunk/doc/performance_tips.xml
Log:
Formatting


Modified: trunk/doc/performance_tips.xml
===================================================================
--- trunk/doc/performance_tips.xml	2018-10-12 21:12:27 UTC (rev 16889)
+++ trunk/doc/performance_tips.xml	2018-10-12 21:15:03 UTC (rev 16890)
@@ -252,9 +252,7 @@
           <listitem>
             <para>
                 If you have lots of RAM and few developers:
-                <programlisting>
-                    SET work_mem TO '256MB';
-                </programlisting>
+                <programlisting>SET work_mem TO '256MB';</programlisting>
             </para>
           </listitem>
         </itemizedlist>
@@ -278,9 +276,7 @@
             <para>
               Recommend 32MB to 1GB on production servers w/lots of RAM, but depends
               on the # of concurrent users.  If you have lots of RAM and few developers:
-                <programlisting>
-                   SET maintenance_work_mem TO '1GB';
-                </programlisting>
+                <programlisting>SET maintenance_work_mem TO '1GB';</programlisting>
             </para>
           </listitem>
         </itemizedlist>
@@ -287,6 +283,8 @@
 
         <para>
           <ulink url="https://www.postgresql.org/docs/current/static/runtime-config-resource.html#GUC-MAX-PARALLEL-WORKERS-PER-GATHER">max_parallel_workers_per_gather</ulink>
+        </para>
+        <para>
           This setting is only available for PostgreSQL 9.6+ and will only affect PostGIS 2.3+, since only PostGIS 2.3+ supports parallel queries.
           If set to higher than 0, then some queries such as those involving relation functions like <code>ST_Intersects</code> can use multiple processes and can run
           more than twice as fast when doing so.  If you have a lot of processors to spare, you should change the value of this to as many processors as you have.



More information about the postgis-tickets mailing list