@@ -63,24 +63,24 @@ PostgreSQL documentation
6363 <para>
6464 If <command>pg_resetxlog</command> complains that it cannot determine
6565 valid data for <filename>pg_control</>, you can force it to proceed anyway
66- by specifying the <literal >-f</> (force) switch . In this case plausible
66+ by specifying the <option >-f</> (force) option . In this case plausible
6767 values will be substituted for the missing data. Most of the fields can be
6868 expected to match, but manual assistance might be needed for the next OID,
6969 next transaction ID and epoch, next multitransaction ID and offset, and
70- WAL starting address fields. These fields can be set using the switches
70+ WAL starting address fields. These fields can be set using the options
7171 discussed below. If you are not able to determine correct values for all
72- these fields, <literal >-f</> can still be used, but
72+ these fields, <option >-f</> can still be used, but
7373 the recovered database must be treated with even more suspicion than
7474 usual: an immediate dump and reload is imperative. <emphasis>Do not</>
7575 execute any data-modifying operations in the database before you dump,
7676 as any such action is likely to make the corruption worse.
7777 </para>
7878
7979 <para>
80- The <literal >-o</>, <literal >-x</>, <literal >-e</>,
81- <literal >-m</>, <literal >-O</>,
82- and <literal >-l</>
83- switches allow the next OID, next transaction ID, next transaction ID's
80+ The <option >-o</>, <option >-x</>, <option >-e</>,
81+ <option >-m</>, <option >-O</>,
82+ and <option >-l</>
83+ options allow the next OID, next transaction ID, next transaction ID's
8484 epoch, next multitransaction ID, next multitransaction offset, and WAL
8585 starting address values to be set manually. These are only needed when
8686 <command>pg_resetxlog</command> is unable to determine appropriate values
@@ -90,12 +90,12 @@ PostgreSQL documentation
9090 <itemizedlist>
9191 <listitem>
9292 <para>
93- A safe value for the next transaction ID (<literal >-x</>)
93+ A safe value for the next transaction ID (<option >-x</>)
9494 can be determined by looking for the numerically largest
9595 file name in the directory <filename>pg_clog</> under the data directory,
9696 adding one,
9797 and then multiplying by 1048576. Note that the file names are in
98- hexadecimal. It is usually easiest to specify the switch value in
98+ hexadecimal. It is usually easiest to specify the option value in
9999 hexadecimal too. For example, if <filename>0011</> is the largest entry
100100 in <filename>pg_clog</>, <literal>-x 0x1200000</> will work (five
101101 trailing zeroes provide the proper multiplier).
@@ -104,29 +104,29 @@ PostgreSQL documentation
104104
105105 <listitem>
106106 <para>
107- A safe value for the next multitransaction ID (<literal >-m</>)
107+ A safe value for the next multitransaction ID (<option >-m</>)
108108 can be determined by looking for the numerically largest
109109 file name in the directory <filename>pg_multixact/offsets</> under the
110110 data directory, adding one, and then multiplying by 65536. As above,
111111 the file names are in hexadecimal, so the easiest way to do this is to
112- specify the switch value in hexadecimal and add four zeroes.
112+ specify the option value in hexadecimal and add four zeroes.
113113 </para>
114114 </listitem>
115115
116116 <listitem>
117117 <para>
118- A safe value for the next multitransaction offset (<literal >-O</>)
118+ A safe value for the next multitransaction offset (<option >-O</>)
119119 can be determined by looking for the numerically largest
120120 file name in the directory <filename>pg_multixact/members</> under the
121121 data directory, adding one, and then multiplying by 65536. As above,
122122 the file names are in hexadecimal, so the easiest way to do this is to
123- specify the switch value in hexadecimal and add four zeroes.
123+ specify the option value in hexadecimal and add four zeroes.
124124 </para>
125125 </listitem>
126126
127127 <listitem>
128128 <para>
129- The WAL starting address (<literal >-l</>) should be
129+ The WAL starting address (<option >-l</>) should be
130130 larger than any WAL segment file name currently existing in
131131 the directory <filename>pg_xlog</> under the data directory.
132132 These names are also in hexadecimal and have three parts. The first
@@ -143,9 +143,9 @@ PostgreSQL documentation
143143 <note>
144144 <para>
145145 <command>pg_resetxlog</command> itself looks at the files in
146- <filename>pg_xlog</> and chooses a default <literal >-l</> setting
146+ <filename>pg_xlog</> and chooses a default <option >-l</> setting
147147 beyond the last existing file name. Therefore, manual adjustment of
148- <literal >-l</> should only be needed if you are aware of WAL segment
148+ <option >-l</> should only be needed if you are aware of WAL segment
149149 files that are not currently present in <filename>pg_xlog</>, such as
150150 entries in an offline archive; or if the contents of
151151 <filename>pg_xlog</> have been lost entirely.
@@ -176,17 +176,17 @@ PostgreSQL documentation
176176 </para>
177177
178178 <para>
179- The <literal >-n</> (no operation) switch instructs
179+ The <option >-n</> (no operation) option instructs
180180 <command>pg_resetxlog</command> to print the values reconstructed from
181181 <filename>pg_control</> and then exit without modifying anything.
182182 This is mainly a debugging tool, but can be useful as a sanity check
183183 before allowing <command>pg_resetxlog</command> to proceed for real.
184184 </para>
185185
186186 <para>
187- The <literal >-V</> and <literal >--version</> options print
187+ The <option >-V</> and <option >--version</> options print
188188 the <application>pg_resetxlog</application> version and exit. The
189- options <literal >-?</> and <literal >--help</> show supported arguments,
189+ options <option >-?</> and <option >--help</> show supported arguments,
190190 and exit.
191191 </para>
192192
0 commit comments