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

Commitb1e2e9c

Browse files
committed
Fix awkward wording in Incrementally Updated Backups docs.
Backpatch to 9.0.X.
1 parentf5878cd commitb1e2e9c

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

‎doc/src/sgml/high-availability.sgml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
<!-- $PostgreSQL: pgsql/doc/src/sgml/high-availability.sgml,v 1.79 2010/08/17 04:37:20 petere Exp $ -->
1+
<!-- $PostgreSQL: pgsql/doc/src/sgml/high-availability.sgml,v 1.80 2010/08/24 15:22:12 momjian Exp $ -->
22

33
<chapter id="high-availability">
44
<title>High Availability, Load Balancing, and Replication</title>
@@ -1957,7 +1957,7 @@ psql -c "select pg_last_xlog_replay_location();" > /path/to/backup/end_location
19571957
progress of the recovery with the stored backup ending WAL location:
19581958
the server is not consistent until recovery has reached the backup end
19591959
location. The progress of the recovery can also be observed with the
1960-
<function>pg_last_xlog_replay_location</> function,but thatrequired
1960+
<function>pg_last_xlog_replay_location</> function,though thatrequires
19611961
connecting to the server while it might not be consistent yet, so
19621962
care should be taken with that method.
19631963
</para>

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp