Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
P
postgres-lambda-diff
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container registry
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Jakob Huber
postgres-lambda-diff
Commits
db1531f6
Commit
db1531f6
authored
20 years ago
by
Neil Conway
Browse files
Options
Downloads
Patches
Plain Diff
Fix typo, other minor improvements.
parent
f6474586
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
doc/src/sgml/wal.sgml
+12
-12
12 additions, 12 deletions
doc/src/sgml/wal.sgml
with
12 additions
and
12 deletions
doc/src/sgml/wal.sgml
+
12
−
12
View file @
db1531f6
<!-- $PostgreSQL: pgsql/doc/src/sgml/wal.sgml,v 1.
29
2004/
08/08 04:34:43 tgl
Exp $ -->
<!-- $PostgreSQL: pgsql/doc/src/sgml/wal.sgml,v 1.
30
2004/
11/15 04:35:57 neilc
Exp $ -->
<chapter id="wal">
<title>Write-Ahead Logging (<acronym>WAL</acronym>)</title>
...
...
@@ -104,17 +104,17 @@
</para>
<para>
<firstterm>Checkpoints</firstterm><indexterm><primary>checkpoint</></>
are points in the sequence of
transactions at which it is guaranteed
that the data files have
been updated with all information logged before
the checkpoint. At
checkpoint time, all dirty data pages are flushed to
disk and a
special checkpoint record is written to the log file. As
result, in
the event of a crash, the recover
er knows from what point in the
log (known as the redo record) it should start the
REDO operation,
since any changes made to data files before that
record are already
on disk. After a checkpoint has been made, any log segments
written
before the redo record are no longer needed and can be recycled
or
removed. (When <acronym>WAL</acronym> archiving is being done, the
<firstterm>Checkpoints</firstterm><indexterm><primary>checkpoint</></>
are points in the sequence of
transactions at which it is guaranteed
that the data files have
been updated with all information logged before
the checkpoint. At
checkpoint time, all dirty data pages are flushed to
disk and a
special checkpoint record is written to the log file. As
a
result, in
the event of a crash, the
crash
recover
y procedure knows from
what point in the
log (known as the redo record) it should start the
REDO operation,
since any changes made to data files before that
point
are already
on disk. After a checkpoint has been made, any log segments
written
before the redo record are no longer needed and can be recycled
or
removed. (When <acronym>WAL</acronym> archiving is being done, the
log segments must be archived before being recycled or removed.)
</para>
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment