Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
P
Postgres FD Implementation
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Analytics
Analytics
CI / CD
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Abuhujair Javed
Postgres FD Implementation
Commits
85f345be
Commit
85f345be
authored
Jan 27, 2011
by
Tom Lane
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Improve grammar and spelling in durability discussion.
parent
b34ee301
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
6 additions
and
5 deletions
+6
-5
doc/src/sgml/perform.sgml
doc/src/sgml/perform.sgml
+6
-5
No files found.
doc/src/sgml/perform.sgml
View file @
85f345be
...
...
@@ -1118,9 +1118,10 @@ SELECT * FROM x, y, a, b, c WHERE something AND somethingelse;
so if your site does not require such a guarantee,
<productname>PostgreSQL</productname> can be configured to run
much faster. The following are configuration changes you can make
to improve performance in such cases; they do not invalidate
commit guarantees related to database crashes, only abrupt operating
system stoppage, except as mentioned below:
to improve performance in such cases. Except as noted below, durability
is still guaranteed in case of a crash of the database software;
only abrupt operating system stoppage creates a risk of data loss
or corruption when these settings are used.
<itemizedlist>
<listitem>
...
...
@@ -1159,8 +1160,8 @@ SELECT * FROM x, y, a, b, c WHERE something AND somethingelse;
<para>
Turn off <xref linkend="guc-synchronous-commit">; there might be no
need to write the <acronym>WAL</acronym> to disk on every
commit. This
does enable possible tranaction loss in case of
a <emphasis>database</> crash
.
commit. This
setting does risk transaction loss (though not data
corruption) in case of a crash of the <emphasis>database</> alone
.
</para>
</listitem>
</itemizedlist>
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment