Named restore point improvements.
Emit a log message when creating a named restore point, and improve documentation for pg_create_restore_point(). Euler Taveira de Oliveira, per suggestions from Thom Brown, with some additional wordsmithing by me.
This commit is contained in:
parent
6079375431
commit
79ad8fc5f8
@ -14069,6 +14069,16 @@ postgres=# select pg_start_backup('label_goes_here');
|
||||
of the transaction log file currently in use.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
<function>pg_create_restore_point</> creates a named transaction log
|
||||
record that can be used as recovery target, and returns the corresponding
|
||||
transaction log location. The given name can then be used with
|
||||
<xref linkend="recovery-target-name"> to specify the point up to which
|
||||
recovery will proceed. Avoid creating multiple restore points with the
|
||||
same name, since recovery will stop at the first one whose name matches
|
||||
the recovery target.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
<function>pg_current_xlog_location</> displays the current transaction log write
|
||||
location in the same format used by the above functions. Similarly,
|
||||
|
@ -8144,6 +8144,10 @@ XLogRestorePoint(const char *rpName)
|
||||
|
||||
RecPtr = XLogInsert(RM_XLOG_ID, XLOG_RESTORE_POINT, &rdata);
|
||||
|
||||
ereport(LOG,
|
||||
(errmsg("restore point \"%s\" created at %X/%X",
|
||||
rpName, RecPtr.xlogid, RecPtr.xrecoff)));
|
||||
|
||||
return RecPtr;
|
||||
}
|
||||
|
||||
|
Loading…
x
Reference in New Issue
Block a user