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

Commit03a68a7

Browse files
committed
Done:
< o Add command to archive partially filled write-ahead logs? [pitr]<< Currently only full WAL files are archived. This means that the< most recent transactions aren't available for recovery in case< of a disk failure.<Reorder:< o %Create dump tool for write-ahead logs for use in determining< transaction id for point-in-time recovery> o %Create dump tool for write-ahead logs for use in determining> transaction id for point-in-time recovery
1 parent2c660c6 commit03a68a7

File tree

2 files changed

+7
-18
lines changed

2 files changed

+7
-18
lines changed

‎doc/TODO

Lines changed: 3 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
PostgreSQL TODO List
33
====================
44
Current maintainer:Bruce Momjian (bruce@momjian.us)
5-
Last updated:Wed Sep20 19:01:42 EDT 2006
5+
Last updated:Tue Sep26 07:18:13 EDT 2006
66

77
The most recent version of this document can be viewed at
88
http://www.postgresql.org/docs/faqs.TODO.html.
@@ -139,19 +139,13 @@ Administration
139139

140140
* Point-In-Time Recovery (PITR)
141141

142-
o Add command to archive partially filled write-ahead logs? [pitr]
143-
144-
Currently only full WAL files are archived. This means that the
145-
most recent transactions aren't available for recovery in case
146-
of a disk failure.
147-
148-
o %Create dump tool for write-ahead logs for use in determining
149-
transaction id for point-in-time recovery
150142
o Allow a warm standby system to also allow read-only statements
151143
[pitr]
152144

153145
This is useful for checking PITR recovery.
154146

147+
o %Create dump tool for write-ahead logs for use in determining
148+
transaction id for point-in-time recovery
155149
o Allow the PITR process to be debugged and data examined
156150

157151

‎doc/src/FAQ/TODO.html

Lines changed: 4 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@
88
<bodybgcolor="#FFFFFF"text="#000000"link="#FF0000"vlink="#A00000"alink="#0000FF">
99
<h1><aname="section_1">PostgreSQL TODO List</a></h1>
1010
<p>Current maintainer: Bruce Momjian (<ahref="mailto:bruce@momjian.us">bruce@momjian.us</a>)<br/>
11-
Last updated:Wed Sep20 19:01:42 EDT 2006
11+
Last updated:Tue Sep26 07:18:13 EDT 2006
1212
</p>
1313
<p>The most recent version of this document can be viewed at<br/>
1414
<ahref="http://www.postgresql.org/docs/faqs.TODO.html">http://www.postgresql.org/docs/faqs.TODO.html</a>.
@@ -127,17 +127,12 @@ <h1><a name="section_2">Administration</a></h1>
127127
</li></ul>
128128
</li><li>Point-In-Time Recovery (PITR)
129129
<ul>
130-
<li>Add command to archive partially filled write-ahead logs? [<ahref="http://momjian.postgresql.org/cgi-bin/pgtodo?pitr">pitr</a>]
131-
<p> Currently only full WAL files are archived. This means that the
132-
most recent transactions aren't available for recovery in case
133-
of a disk failure.
134-
</p>
135-
</li><li>%Create dump tool for write-ahead logs for use in determining
136-
transaction id for point-in-time recovery
137-
</li><li>Allow a warm standby system to also allow read-only statements
130+
<li>Allow a warm standby system to also allow read-only statements
138131
[<ahref="http://momjian.postgresql.org/cgi-bin/pgtodo?pitr">pitr</a>]
139132
<p> This is useful for checking PITR recovery.
140133
</p>
134+
</li><li>%Create dump tool for write-ahead logs for use in determining
135+
transaction id for point-in-time recovery
141136
</li><li>Allow the PITR process to be debugged and data examined
142137
</li></ul>
143138
</li></ul>

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp