database/postgres
database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-04-22 23:02:54 +03:00
Code

doc: Reorganize pg_resetxlog reference page

Browse Source 
The pg_resetxlog reference page didn't have a proper options list, only
running text listing the options and some explanations of them.  This
might have worked when there were only a few options, but the list has
grown over the releases, and now it's hard to find an option and its
associated explanation.  So write out the options list as on other
reference pages.
This commit is contained in:
Peter Eisentraut 2016-02-29 18:48:34 -05:00
parent 28f6df3c36
commit e19e4cf0be
1 changed files with 151 additions and 85 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

236
doc/src/sgml/ref/pg_resetxlog.sgml
View File

@ -22,15 +22,9 @@ PostgreSQL documentation
<refsynopsisdiv> <refsynopsisdiv>
<cmdsynopsis> <cmdsynopsis>
<command>pg_resetxlog</command> <command>pg_resetxlog</command>
<arg choice="opt"><option>-c</option> <replaceable class="parameter">xid</replaceable>,<replaceable class="parameter">xid</replaceable></arg>
<arg choice="opt"><option>-f</option></arg> <arg choice="opt"><option>-f</option></arg>
<arg choice="opt"><option>-n</option></arg> <arg choice="opt"><option>-n</option></arg>
<arg choice="opt"><option>-o</option> <replaceable class="parameter">oid</replaceable></arg> <arg rep="repeat"><replaceable>option</replaceable></arg>
<arg choice="opt"><option>-x</option> <replaceable class="parameter">xid</replaceable></arg>
<arg choice="opt"><option>-e</option> <replaceable class="parameter">xid_epoch</replaceable></arg>
<arg choice="opt"><option>-m</option> <replaceable class="parameter">mxid</replaceable>,<replaceable class="parameter">mxid</replaceable></arg>
<arg choice="opt"><option>-O</option> <replaceable class="parameter">mxoff</replaceable></arg>
<arg choice="opt"><option>-l</option> <replaceable class="parameter">xlogfile</replaceable></arg>
<arg choice="req"><arg choice="opt"><option>-D</option></arg> <replaceable class="parameter">datadir</replaceable></arg> <arg choice="req"><arg choice="opt"><option>-D</option></arg> <replaceable class="parameter">datadir</replaceable></arg>
</cmdsynopsis> </cmdsynopsis>
</refsynopsisdiv> </refsynopsisdiv>
@ -76,78 +70,108 @@ PostgreSQL documentation
execute any data-modifying operations in the database before you dump, execute any data-modifying operations in the database before you dump,
as any such action is likely to make the corruption worse. as any such action is likely to make the corruption worse.
</para> </para>
</refsect1>
<refsect1>
<title>Options</title>
<variablelist>
<varlistentry>
<term><option>-f</option></term>
<listitem>
<para>
Force <command>pg_resetxlog</command> to proceed even if it cannot determine
valid data for <filename>pg_control</>, as explained above.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term><option>-n</option></term>
<listitem>
<para>
The <option>-n</> (no operation) option instructs
<command>pg_resetxlog</command> to print the values reconstructed from
<filename>pg_control</> and values about to be changed, and then exit
without modifying anything. This is mainly a debugging tool, but can be
useful as a sanity check before allowing <command>pg_resetxlog</command>
to proceed for real.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term><option>-V</option></term>
<term><option>--version</option></term>
<listitem><para>Display version information, then exit.</para></listitem>
</varlistentry>
<varlistentry>
<term><option>-?</option></term>
<term><option>--help</option></term>
<listitem><para>Show help, then exit.</para></listitem>
</varlistentry>
</variablelist>
<para> <para>
The <option>-o</>, <option>-x</>, <option>-e</>, The following options are only needed when
<option>-m</>, <option>-O</>,
<option>-c</>
and <option>-l</>
options allow the next OID, next transaction ID, next transaction ID's
epoch, next and oldest multitransaction ID, next multitransaction offset,
oldest and newest transaction IDs for which the commit time can be retrieved,
and WAL
starting address values to be set manually. These are only needed when
<command>pg_resetxlog</command> is unable to determine appropriate values <command>pg_resetxlog</command> is unable to determine appropriate values
by reading <filename>pg_control</>. Safe values can be determined as by reading <filename>pg_control</>. Safe values can be determined as
follows: described below. For values that take numeric arguments, hexadecimal
values can be specified by using the prefix <literal>0x</literal>.
</para>
<itemizedlist> <variablelist>
<varlistentry>
<term><option>-c</option> <replaceable class="parameter">xid</replaceable>,<replaceable class="parameter">xid</replaceable></term>
<listitem> <listitem>
<para> <para>
A safe value for the next transaction ID (<option>-x</>) Manually set the oldest and newest transaction IDs for which the commit
can be determined by looking for the numerically largest time can be retrieved.
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 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).
</para> </para>
</listitem>
<listitem>
<para>
A safe value for the next multitransaction ID (first part of <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.
Conversely, a safe value for the oldest multitransaction ID (second part of
<option>-m</>)
can be determined by looking for the numerically smallest
file name in the same directory and multiplying by 65536.
As above, the file names are in hexadecimal, so the easiest way to do
this is to specify the option value in hexadecimal and append four zeroes.
</para>
</listitem>
<listitem>
<para>
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 52352. As above,
the file names are in hexadecimal. There is no simple recipe such as
the ones above of appending zeroes.
</para>
</listitem>
<listitem>
<para> <para>
A safe value for the oldest transaction ID for which the commit time can A safe value for the oldest transaction ID for which the commit time can
be retrieved (first part of <option>-c</>) can be determined by looking be retrieved (first part) can be determined by looking
for the numerically smallest file name in the directory for the numerically smallest file name in the directory
<filename>pg_commit_ts</> under the data directory. Conversely, a safe <filename>pg_commit_ts</> under the data directory. Conversely, a safe
value for the newest transaction ID for which the commit time can be value for the newest transaction ID for which the commit time can be
retrieved (second part of <option>-c</>) can be determined by looking for retrieved (second part) can be determined by looking for the numerically
the numerically greatest file name in the same directory. As above, the greatest file name in the same directory. The file names are in
file names are in hexadecimal. hexadecimal.
</para> </para>
</listitem> </listitem>
</varlistentry>
<varlistentry>
<term><option>-e</option> <replaceable class="parameter">xid_epoch</replaceable></term>
<listitem> <listitem>
<para> <para>
The WAL starting address (<option>-l</>) should be Manually set the next transaction ID's epoch.
</para>
<para>
The transaction ID epoch is not actually stored anywhere in the database
except in the field that is set by <command>pg_resetxlog</command>,
so any value will work so far as the database itself is concerned.
You might need to adjust this value to ensure that replication
systems such as <application>Slony-I</> and
<application>Skytools</> work correctly &mdash;
if so, an appropriate value should be obtainable from the state of
the downstream replicated database.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term><option>-l</option> <replaceable class="parameter">xlogfile</replaceable></term>
<listitem>
<para>
Manually set the WAL starting address.
</para>
<para>
The WAL starting address should be
larger than any WAL segment file name currently existing in larger than any WAL segment file name currently existing in
the directory <filename>pg_xlog</> under the data directory. the directory <filename>pg_xlog</> under the data directory.
These names are also in hexadecimal and have three parts. The first These names are also in hexadecimal and have three parts. The first
@ -168,46 +192,81 @@ PostgreSQL documentation
</para> </para>
</note> </note>
</listitem> </listitem>
</varlistentry>
<varlistentry>
<term><option>-m</option> <replaceable class="parameter">mxid</replaceable>,<replaceable class="parameter">mxid</replaceable></term>
<listitem> <listitem>
<para>
Manually set the next and oldest multitransaction ID.
</para>
<para>
A safe value for the next multitransaction ID (first part) 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 (0x10000). Conversely, a safe
value for the oldest multitransaction ID (second part of
<option>-m</>) can be determined by looking for the numerically smallest
file name in the same directory and multiplying by 65536. The file
names are in hexadecimal, so the easiest way to do this is to specify
the option value in hexadecimal and append four zeroes.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term><option>-o</option> <replaceable class="parameter">oid</replaceable></term>
<listitem>
<para>
Manually set the next OID.
</para>
<para> <para>
There is no comparably easy way to determine a next OID that's beyond There is no comparably easy way to determine a next OID that's beyond
the largest one in the database, but fortunately it is not critical to the largest one in the database, but fortunately it is not critical to
get the next-OID setting right. get the next-OID setting right.
</para> </para>
</listitem> </listitem>
</varlistentry>
<varlistentry>
<term><option>-O</option> <replaceable class="parameter">mxoff</replaceable></term>
<listitem> <listitem>
<para> <para>
The transaction ID epoch is not actually stored anywhere in the database Manually set the next multitransaction offset.
except in the field that is set by <command>pg_resetxlog</command>, </para>
so any value will work so far as the database itself is concerned.
You might need to adjust this value to ensure that replication <para>
systems such as <application>Slony-I</> and A safe value can be determined by looking for the numerically largest
<application>Skytools</> work correctly &mdash; file name in the directory <filename>pg_multixact/members</> under the
if so, an appropriate value should be obtainable from the state of data directory, adding one, and then multiplying by 52352 (0xCC80).
the downstream replicated database. The file names are in hexadecimal. There is no simple recipe such as
the ones for other options of appending zeroes.
</para> </para>
</listitem> </listitem>
</itemizedlist> </varlistentry>
</para>
<para> <varlistentry>
The <option>-n</> (no operation) option instructs <term><option>-x</option> <replaceable class="parameter">xid</replaceable></term>
<command>pg_resetxlog</command> to print the values reconstructed from <listitem>
<filename>pg_control</> and values about to be changed, and then exit <para>
without modifying anything. This is mainly a debugging tool, but can be Manually set the next transaction ID.
useful as a sanity check before allowing <command>pg_resetxlog</command> </para>
to proceed for real.
</para>
<para>
The <option>-V</> and <option>--version</> options print
the <application>pg_resetxlog</application> version and exit. The
options <option>-?</> and <option>--help</> show supported arguments,
and exit.
</para>
<para>
A safe value 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 (0x100000). Note that the file names are 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).
</para>
</listitem>
</varlistentry>
</variablelist>
</refsect1> </refsect1>
<refsect1> <refsect1>
@ -224,4 +283,11 @@ PostgreSQL documentation
</para> </para>
</refsect1> </refsect1>
<refsect1>
<title>See Also</title>
<simplelist type="inline">
<member><xref linkend="app-pgcontroldata"></member>
</simplelist>
</refsect1>
</refentry> </refentry>