<arg choice="opt"><option>-o</option> <replaceable class="parameter">oid</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></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="plain"><replaceable>datadir</replaceable></arg>

<option>-m</>, <option>-O</>,

and <option>-l</>

options allow the next OID, next transaction ID, next transaction ID's

epoch, next multitransaction ID, next multitransaction offset, and WAL

epoch, nextand oldestmultitransaction 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

by reading <filename>pg_control</>. Safe values can be determined as

<listitem>

<para>

A safe value for the next multitransaction ID (<option>-m</>)

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. As above,

the file names are in hexadecimal, so the easiest way to do this is to

specify the option value in hexadecimal and add four zeroes.

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>

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 by65536. As above,

the file names are in hexadecimal, so the easiest way to do this is to

specifytheoption value in hexadecimal and add four zeroes.

data directory, adding one, and then multiplying by52352. As above,

the file names are in hexadecimal. There is no simple recipe such as

theones above of appending zeroes.

</para>

</listitem>

printf(_(" -e XIDEPOCH set next transaction ID epoch\n"));

printf(_(" -f force update to be done\n"));

printf(_(" -l XLOGFILE force minimum WAL starting location for new transaction log\n"));

printf(_(" -m XID,OLDESTset next multitransaction IDand oldestvalue\n"));

printf(_(" -m XID,XID set nextand oldestmultitransaction ID\n"));

printf(_(" -n no update, just show extracted control values (for testing)\n"));

printf(_(" -o OID set next OID\n"));

printf(_(" -O OFFSET set next multitransaction offset\n"));