Update ref/pgtesttiming.sgml

ref/pgtesttiming.sgml 调整内容191215：

row178————————————————
	根据WinMerge比较结果，将
		"<screen>"
		调整为新内容
		"<screen><![CDATA["
row194
	根据row178英文内容更新，将
		"<screen>"
		调整为新翻译内容
		"<screen><![CDATA["

row188————————————————
	根据WinMerge比较结果，将
		"</screen>"
		调整为新内容
		"]]></screen>"
row204
	根据row188英文内容更新，将
		"</screen>"
		调整为新内容
		"]]></screen>"

row281————————————————
	根据WinMerge比较结果，将
		"<screen>"
		调整为新内容
		"<screen><![CDATA["
row300
	根据row281英文内容更新，将
		"<screen>"
		调整为新翻译内容
		"<screen><![CDATA["

row294————————————————
	根据WinMerge比较结果，将
		"</screen>"
		调整为新内容
		"]]></screen>"
row313
	根据row294英文内容更新，将
		"</screen>"
		调整为新内容
		"]]></screen>"

row370————————————————
	根据WinMerge比较结果，将
		"<screen>"
		调整为新内容
		"<screen><![CDATA["
row392
	根据row370英文内容更新，将
		"<screen>"
		调整为新翻译内容
		"<screen><![CDATA["

row387————————————————
	根据WinMerge比较结果，将
		"</screen></para>"
		调整为新内容
		"]]></screen></para>"
row409
	根据row387英文内容更新，将
		"</screen></para>"
		调整为新翻译内容
		"]]></screen></para>"

其他更新
	将英文原文中的</>补充相应tag

Author: chegong18

postgresql/doc/src/sgml/ref/pgtesttiming.sgml

@@ -55,7 +55,7 @@ ____________________________________________________________________________-->
 
 <!--==========================orignal english content==========================
  <para>
-  <application>pg_test_timing</> is a tool to measure the timing overhead
+  <application>pg_test_timing</application> is a tool to measure the timing overhead
   on your system and confirm that the system time never moves backwards.
   Systems that are slow to collect timing data can give less accurate
   <command>EXPLAIN ANALYZE</command> results.
@@ -93,8 +93,8 @@ ____________________________________________________________________________-->
      </varlistentry>
 
      <varlistentry>
-      <term><option>-V</></term>
-      <term><option>-&minus;version</></term>
+      <term><option>-V</option></term>
+      <term><option>-&minus;version</option></term>
       <listitem>
        <para>
         Print the <application>pg_test_timing</application> version and exit.
@@ -103,8 +103,8 @@ ____________________________________________________________________________-->
      </varlistentry>
 
      <varlistentry>
-      <term><option>-?</></term>
-      <term><option>-&minus;help</></term>
+      <term><option>-?</option></term>
+      <term><option>-&minus;help</option></term>
       <listitem>
        <para>
         Show help about <application>pg_test_timing</application> command line
@@ -175,7 +175,7 @@ ____________________________________________________________________________-->
    nanoseconds. This example from an Intel i7-860 system using a TSC clock
    source shows excellent performance:
 
-<screen>
+<screen><![CDATA[
 Testing timing overhead for 3 seconds.
 Per loop time including overhead: 35.96 ns
 Histogram of timing durations:
@@ -185,13 +185,13 @@ Histogram of timing durations:
      4      0.00015        126
      8      0.00002         13
     16      0.00000          2
-</screen>
+]]></screen>
   </para>
 ____________________________________________________________________________-->
   <para>
    好的结果将显示大部分（>90%）的单个计时调用用时都小于 1 微秒。每次循环的平均开销将会更低，低于 100 纳秒。下面的例子来自于一台使用了一份 TSC 时钟源码的 Intel i7-860 系统，它展示了非常好的性能：
 
-<screen>
+<screen><![CDATA[
 Testing timing overhead for 3 seconds.
 Per loop time including overhead: 35.96 ns
 Histogram of timing durations:
@@ -201,7 +201,7 @@ Histogram of timing durations:
      4      0.00015        126  
      8      0.00002         13  
     16      0.00000          2  
-</screen>
+]]></screen>
   </para>
 
 <!--==========================orignal english content==========================
@@ -278,7 +278,7 @@ ____________________________________________________________________________-->
    possible from switching to the slower acpi_pm time source, on the same
    system used for the fast results above:
 
-<screen>
+<screen><![CDATA[
 # cat /sys/devices/system/clocksource/clocksource0/available_clocksource
 tsc hpet acpi_pm
 # echo acpi_pm > /sys/devices/system/clocksource/clocksource0/current_clocksource
@@ -291,13 +291,13 @@ Histogram of timing durations:
      4      0.07810       3241
      8      0.01357        563
     16      0.00007          3
-</screen>
+]]></screen>
   </para>
 ____________________________________________________________________________-->
   <para>
    在一些较新的 Linux 系统上，可以在任何时候更改用来收集计时数据的时钟来源。第二个例子显示了在上述快速结果的相同系统上切换到较慢的 acpi_pm 时间源可能带来的降速：
 
-<screen>
+<screen><![CDATA[
 # cat /sys/devices/system/clocksource/clocksource0/available_clocksource
 tsc hpet acpi_pm
 # echo acpi_pm > /sys/devices/system/clocksource/clocksource0/current_clocksource
@@ -310,7 +310,7 @@ Histogram of timing durations:
      4      0.07810       3241  
      8      0.01357        563  
     16      0.00007          3  
-</screen>
+]]></screen>
   </para>
 
 <!--==========================orignal english content==========================
@@ -367,7 +367,7 @@ kern.timecounter.hardware: ACPI-fast -> TSC
    implementation, which can have good resolution when it's backed by fast
    enough timing hardware, as in this example:
 
-<screen>
+<screen><![CDATA[
 $ cat /sys/devices/system/clocksource/clocksource0/available_clocksource
 jiffies
 $ dmesg | grep time.c
@@ -384,12 +384,12 @@ Histogram of timing durations:
      8      0.00007         22
     16      0.00000          1
     32      0.00000          1
-</screen></para>
+]]></screen></para>
 ____________________________________________________________________________-->
   <para>
    其他系统可能只允许在启动时设定时间源。在旧的 Linux 系统上，“clock”内核设置是做这类更改的唯一方法。并且即使在一些更近的系统上，对于一个时钟源你将只能看到唯一的选项 "jiffies"。Jiffies 是老的 Linux 软件时钟实现，当有足够快的计时硬件支持时，它能够具有很好的解析度，就像在这个例子中：
 
-<screen>
+<screen><![CDATA[
 $ cat /sys/devices/system/clocksource/clocksource0/available_clocksource
 jiffies
 $ dmesg | grep time.c
@@ -406,7 +406,7 @@ Histogram of timing durations:
      8      0.00007         22  
     16      0.00000          1  
     32      0.00000          1  
-</screen></para>
+]]></screen></para>
 
  </refsect2>