@ -63,13 +63,13 @@ PostgreSQL documentation
<para>
If <command>pg_resetxlog</command> complains that it cannot determine
valid data for <filename>pg_control</>, you can force it to proceed anyway
by specifying the <literal>-f</> (force) switch . In this case plausible
by specifying the <option>-f</> (force) option . In this case plausible
values will be substituted for the missing data. Most of the fields can be
expected to match, but manual assistance might be needed for the next OID,
next transaction ID and epoch, next multitransaction ID and offset, and
WAL starting address fields. These fields can be set using the switche s
WAL starting address fields. These fields can be set using the option s
discussed below. If you are not able to determine correct values for all
these fields, <literal >-f</> can still be used, but
these fields, <option >-f</> can still be used, but
the recovered database must be treated with even more suspicion than
usual: an immediate dump and reload is imperative. <emphasis>Do not</>
execute any data-modifying operations in the database before you dump,
@ -77,10 +77,10 @@ PostgreSQL documentation
</para>
<para>
The <literal>-o</>, <literal>-x</>, <literal >-e</>,
<literal>-m</>, <literal >-O</>,
and <literal >-l</>
switche s allow the next OID, next transaction ID, next transaction ID's
The <option>-o</>, <option>-x</>, <option >-e</>,
<option>-m</>, <option >-O</>,
and <option >-l</>
option s allow the next OID, next transaction ID, next transaction ID's
epoch, next multitransaction ID, next multitransaction offset, and WAL
starting address values to be set manually. These are only needed when
<command>pg_resetxlog</command> is unable to determine appropriate values
@ -90,12 +90,12 @@ PostgreSQL documentation
<itemizedlist>
<listitem>
<para>
A safe value for the next transaction ID (<literal >-x</>)
A safe value for the next transaction ID (<option >-x</>)
can be determined by looking for the numerically largest
file name in the directory <filename>pg_clog</> under the data directory,
adding one,
and then multiplying by 1048576. Note that the file names are in
hexadecimal. It is usually easiest to specify the switch value in
hexadecimal. It is usually easiest to specify the option value in
hexadecimal too. For example, if <filename>0011</> is the largest entry
in <filename>pg_clog</>, <literal>-x 0x1200000</> will work (five
trailing zeroes provide the proper multiplier).
@ -104,29 +104,29 @@ PostgreSQL documentation
<listitem>
<para>
A safe value for the next multitransaction ID (<literal >-m</>)
A safe value for the next multitransaction ID (<option >-m</>)
can be determined by looking for the numerically largest
file name in the directory <filename>pg_multixact/offsets</> under the
data directory, adding one, and then multiplying by 65536. As above,
the file names are in hexadecimal, so the easiest way to do this is to
specify the switch value in hexadecimal and add four zeroes.
specify the option value in hexadecimal and add four zeroes.
</para>
</listitem>
<listitem>
<para>
A safe value for the next multitransaction offset (<literal >-O</>)
A safe value for the next multitransaction offset (<option >-O</>)
can be determined by looking for the numerically largest
file name in the directory <filename>pg_multixact/members</> under the
data directory, adding one, and then multiplying by 65536. As above,
the file names are in hexadecimal, so the easiest way to do this is to
specify the switch value in hexadecimal and add four zeroes.
specify the option value in hexadecimal and add four zeroes.
</para>
</listitem>
<listitem>
<para>
The WAL starting address (<literal >-l</>) should be
The WAL starting address (<option >-l</>) should be
larger than any WAL segment file name currently existing in
the directory <filename>pg_xlog</> under the data directory.
These names are also in hexadecimal and have three parts. The first
@ -143,9 +143,9 @@ PostgreSQL documentation
<note>
<para>
<command>pg_resetxlog</command> itself looks at the files in
<filename>pg_xlog</> and chooses a default <literal >-l</> setting
<filename>pg_xlog</> and chooses a default <option >-l</> setting
beyond the last existing file name. Therefore, manual adjustment of
<literal >-l</> should only be needed if you are aware of WAL segment
<option >-l</> should only be needed if you are aware of WAL segment
files that are not currently present in <filename>pg_xlog</>, such as
entries in an offline archive; or if the contents of
<filename>pg_xlog</> have been lost entirely.
@ -176,7 +176,7 @@ PostgreSQL documentation
</para>
<para>
The <literal>-n</> (no operation) switch instructs
The <option>-n</> (no operation) option instructs
<command>pg_resetxlog</command> to print the values reconstructed from
<filename>pg_control</> and then exit without modifying anything.
This is mainly a debugging tool, but can be useful as a sanity check
@ -184,9 +184,9 @@ PostgreSQL documentation
</para>
<para>
The <literal>-V</> and <literal >--version</> options print
The <option>-V</> and <option >--version</> options print
the <application>pg_resetxlog</application> version and exit. The
options <literal>-?</> and <literal >--help</> show supported arguments,
options <option>-?</> and <option >--help</> show supported arguments,
and exit.
</para>
Peter Eisentraut
13 years ago