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

Commitd304067

Browse files
committed
Update PITR TODO items:
< failure.> failure. This could be triggered by a user command or a timer.< * Force archiving of partially-full WAL files when pg_stop_backup() is< called or the server is stopped> * Automatically force archiving of partially-filled WAL files when> pg_stop_backup() is called or the server is stopped
1 parent54fe332 commitd304067

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

‎doc/TODO

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
PostgreSQL TODO List
33
====================
44
Current maintainer:Bruce Momjian (pgman@candle.pha.pa.us)
5-
Last updated:Mon Apr 1810:42:34 EDT 2005
5+
Last updated:Mon Apr 1811:03:14 EDT 2005
66

77
The most recent version of this document can be viewed at the PostgreSQL web
88
site, http://www.PostgreSQL.org.
@@ -109,10 +109,10 @@ Administration
109109

110110
Currently only full WAL files are archived. This means that the most
111111
recent transactions aren't available for recovery in case of a disk
112-
failure.
112+
failure. This could be triggered by a user command or a timer.
113113

114-
*Forcearchiving of partially-full WAL files whenpg_stop_backup() is
115-
called or the server is stopped
114+
*Automatically forcearchiving of partially-filled WAL files when
115+
pg_stop_backup() iscalled or the server is stopped
116116

117117
Doing this will allow administrators to know more easily when the
118118
archive contins all the files needed for point-in-time recovery.

0 commit comments

Comments
 (0)
[8]ページ先頭
©2009-2025 Movatter.jp