--On 12. Dezember 2013 10:56:36 +0000 Simon Riggs <[email protected]>
wrote:
Set min_recovery_apply_delay to force a delay in recovery apply for
commit and restore point WAL records. Other records are replayed
immediately. Delay is measured between WAL record time and local standby
time.
There's a small typo in the first paragraph, "paramater" should be
"parameter":
diff --git a/doc/src/sgml/recovery-config.sgml
b/doc/src/sgml/recovery-config.sgml
new file mode 100644
index ee5dc86..550cdce
*** a/doc/src/sgml/recovery-config.sgml
--- b/doc/src/sgml/recovery-config.sgml
*************** restore_command = 'copy "C:\\server\\arc
*** 152,158 ****
By default, a standby server keeps restoring WAL records from the
primary as soon as possible. It may be useful to have a
time-delayed
copy of the data, offering various options to correct data loss
errors.
! This paramater allows you to delay recovery by a fixed period of
time,
specified in milliseconds if no unit is specified. For example,
if
you set this parameter to <literal>5min</literal>, the standby
will
replay each transaction commit only when the system time on the
standby
--- 152,158 ----
By default, a standby server keeps restoring WAL records from the
primary as soon as possible. It may be useful to have a
time-delayed
copy of the data, offering various options to correct data loss
errors.
! This parameter allows you to delay recovery by a fixed period of
time,
specified in milliseconds if no unit is specified. For example,
if
you set this parameter to <literal>5min</literal>, the standby
will
replay each transaction commit only when the system time on the
standby
--
Thanks
Bernd
--
Sent via pgsql-committers mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-committers
