@@ -27,7 +27,7 @@ PostgreSQL documentation
27
27
<arg choice="opt"><option>-o</option> <replaceable class="parameter">oid</replaceable></arg>
28
28
<arg choice="opt"><option>-x</option> <replaceable class="parameter">xid</replaceable></arg>
29
29
<arg choice="opt"><option>-e</option> <replaceable class="parameter">xid_epoch</replaceable></arg>
30
- <arg choice="opt"><option>-m</option> <replaceable class="parameter">mxid</replaceable></arg>
30
+ <arg choice="opt"><option>-m</option> <replaceable class="parameter">mxid</replaceable>,<replaceable class="parameter">mxid</replaceable> </arg>
31
31
<arg choice="opt"><option>-O</option> <replaceable class="parameter">mxoff</replaceable></arg>
32
32
<arg choice="opt"><option>-l</option> <replaceable class="parameter">xlogfile</replaceable></arg>
33
33
<arg choice="plain"><replaceable>datadir</replaceable></arg>
@@ -81,7 +81,7 @@ PostgreSQL documentation
81
81
<option>-m</>, <option>-O</>,
82
82
and <option>-l</>
83
83
options allow the next OID, next transaction ID, next transaction ID's
84
- epoch, next multitransaction ID, next multitransaction offset, and WAL
84
+ epoch, next and oldest multitransaction ID, next multitransaction offset, and WAL
85
85
starting address values to be set manually. These are only needed when
86
86
<command>pg_resetxlog</command> is unable to determine appropriate values
87
87
by reading <filename>pg_control</>. Safe values can be determined as
@@ -104,12 +104,16 @@ PostgreSQL documentation
104
104
105
105
<listitem>
106
106
<para>
107
- A safe value for the next multitransaction ID (<option>-m</>)
107
+ A safe value for the next multitransaction ID (first part of <option>-m</>)
108
108
can be determined by looking for the numerically largest
109
109
file name in the directory <filename>pg_multixact/offsets</> under the
110
- data directory, adding one, and then multiplying by 65536. As above,
111
- the file names are in hexadecimal, so the easiest way to do this is to
112
- specify the option value in hexadecimal and add four zeroes.
110
+ data directory, adding one, and then multiplying by 65536.
111
+ Conversely, a safe value for the oldest multitransaction ID (second part of
112
+ <option>-m</>)
113
+ can be determined by looking for the numerically smallest
114
+ file name in the same directory and multiplying by 65536.
115
+ As above, the file names are in hexadecimal, so the easiest way to do
116
+ this is to specify the option value in hexadecimal and append four zeroes.
113
117
</para>
114
118
</listitem>
115
119
@@ -118,9 +122,9 @@ PostgreSQL documentation
118
122
A safe value for the next multitransaction offset (<option>-O</>)
119
123
can be determined by looking for the numerically largest
120
124
file name in the directory <filename>pg_multixact/members</> under the
121
- data directory, adding one, and then multiplying by 65536 . As above,
122
- the file names are in hexadecimal, so the easiest way to do this is to
123
- specify the option value in hexadecimal and add four zeroes.
125
+ data directory, adding one, and then multiplying by 52352 . As above,
126
+ the file names are in hexadecimal. There is no simple recipe such as
127
+ the ones above of appending zeroes.
124
128
</para>
125
129
</listitem>
126
130
0 commit comments