@@ -62,7 +62,7 @@ PostgreSQL documentation
62
62
values will be substituted for the missing data. Most of the fields can be
63
63
expected to match, but manual assistance might be needed for the next OID,
64
64
next transaction ID and epoch, next multitransaction ID and offset, and
65
- WAL starting address fields. These fields can be set using the options
65
+ WAL starting location fields. These fields can be set using the options
66
66
discussed below. If you are not able to determine correct values for all
67
67
these fields, <option>-f</option> can still be used, but
68
68
the recovered database must be treated with even more suspicion than
@@ -167,11 +167,12 @@ PostgreSQL documentation
167
167
<term><option>-l</option> <replaceable class="parameter">walfile</replaceable></term>
168
168
<listitem>
169
169
<para>
170
- Manually set the WAL starting address.
170
+ Manually set the WAL starting location by specifying the name of the
171
+ next WAL segment file.
171
172
</para>
172
173
173
174
<para>
174
- The WAL starting address should be
175
+ The name of next WAL segment file should be
175
176
larger than any WAL segment file name currently existing in
176
177
the directory <filename>pg_wal</filename> under the data directory.
177
178
These names are also in hexadecimal and have three parts. The first
@@ -180,6 +181,13 @@ PostgreSQL documentation
180
181
largest entry in <filename>pg_wal</filename>, use <literal>-l 00000001000000320000004B</literal> or higher.
181
182
</para>
182
183
184
+ <para>
185
+ Note that when using nondefault WAL segment sizes, the numbers in the WAL
186
+ file names are different from the LSNs that are reported by system
187
+ functions and system views. This option takes a WAL file name, not an
188
+ LSN.
189
+ </para>
190
+
183
191
<note>
184
192
<para>
185
193
<command>pg_resetwal</command> itself looks at the files in
0 commit comments