100
<term><option>-s <replaceable class="parameter">interval</replaceable></option></term>
101
<term><option>--status-interval=<replaceable class="parameter">interval</replaceable></option></term>
104
Specifies the number of seconds between status packets sent back to the
105
server. This allows for easier monitoring of the progress from server.
106
A value of zero disables the periodic status updates completely,
107
although an update will still be sent when requested by the server, to
108
avoid timeout disconnect. The default value is 10 seconds.
114
<term><option>-S <replaceable>slotname</replaceable></option></term>
115
<term><option>--slot=<replaceable class="parameter">slotname</replaceable></option></term>
118
Require <application>pg_receivexlog</application> to use an existing
119
replication slot (see <xref linkend="streaming-replication-slots">).
120
When this option is used, <application>pg_receivexlog</> will report
121
a flush position to the server, indicating when each segment has been
122
synchronized to disk so that the server can remove that segment if it
123
is not otherwise needed. When using this parameter, it is important
124
to make sure that <application>pg_receivexlog</> cannot become the
125
synchronous standby through an incautious setting of
126
<xref linkend="guc-synchronous-standby-names">; it does not flush
127
data frequently enough for this to work correctly.
109
133
<term><option>-v</option></term>
110
134
<term><option>--verbose</option></term>
170
<term><option>-s <replaceable class="parameter">interval</replaceable></option></term>
171
<term><option>--status-interval=<replaceable class="parameter">interval</replaceable></option></term>
174
Specifies the number of seconds between status packets sent back to the
175
server. This allows for easier monitoring of the progress from server.
176
A value of zero disables the periodic status updates completely,
177
although an update will still be sent when requested by the server, to
178
avoid timeout disconnect. The default value is 10 seconds.
184
192
<term><option>-U <replaceable>username</replaceable></option></term>
185
193
<term><option>--username=<replaceable class="parameter">username</replaceable></option></term>
230
<term><option>-S <replaceable>slotname</replaceable></option></term>
231
<term><option>--slot=<replaceable class="parameter">slotname</replaceable></option></term>
234
Require <application>pg_receivexlog</application> to use an existing
235
replication slot (see <xref linkend="streaming-replication-slots">).
236
When this option is used, <application>pg_receivexlog</> will report
237
a flush position to the server, indicating when each segment has been
238
synchronized to disk so that the server can remove that segment if it
239
is not otherwise needed. When using this parameter, it is important
240
to make sure that <application>pg_receivexlog</> cannot become the
241
synchronous standby through an incautious setting of
242
<xref linkend="guc-synchronous-standby-names">; it does not flush
243
data frequently enough for this to work correctly.
295
284
When using <application>pg_receivexlog</application> instead of
296
<xref linkend="guc-archive-command">, the server will continue to
297
recycle transaction log files even if the backups are not properly
298
archived, since there is no command that fails. This can be worked
299
around by having an <xref linkend="guc-archive-command"> that fails
300
when the file has not been properly archived yet, for example:
302
archive_command = 'sleep 5 && test -f /mnt/server/archivedir/%f'
304
The initial timeout is necessary because
305
<application>pg_receivexlog</application> works using asynchronous
306
replication and can therefore be slightly behind the master.
285
<xref linkend="guc-archive-command"> as the main WAL backup method, it is
286
strongly recommended to use replication slots. Otherwise, the server is
287
free to recycle or remove transaction log files before they are backed up,
288
because it does not have any information, either
289
from <xref linkend="guc-archive-command"> or the replication slots, about
290
how far the WAL stream has been archived. Note, however, that a
291
replication slot will fill up the server's disk space if the receiver does
292
not keep up with fetching the WAL data.