Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commit18b9850

Browse files
committed
Clarify name of file to be checked for PITR expiring.
1 parent1a6ad66 commit18b9850

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

‎doc/src/sgml/backup.sgml

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
<!--
2-
$PostgreSQL: pgsql/doc/src/sgml/backup.sgml,v 2.60 2005/03/23 19:38:53 tgl Exp $
2+
$PostgreSQL: pgsql/doc/src/sgml/backup.sgml,v 2.61 2005/04/17 03:05:19 momjian Exp $
33
-->
44
<chapter id="backup">
55
<title>Backup and Restore</title>
@@ -733,8 +733,8 @@ SELECT pg_stop_backup();
733733
the backup history file will be named something like
734734
<literal>0000000100001234000055CD.007C9330.backup</>. (The second part of
735735
this file name stands for an exact position within the WAL file, and can
736-
ordinarily be ignored.) Once you have safely archivedthe backup dump
737-
file, you can delete all archived WAL segments with names numerically
736+
ordinarily be ignored.) Once you have safely archivedthis WAL
737+
segmentfile, you can delete all archived WAL segments with names numerically
738738
preceding this one. The backup history file is just a small text file.
739739
It contains the label string you gave to <function>pg_start_backup</>, as
740740
well as the starting and ending times of the backup. If you used the

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp