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
c441e26e
Commit
c441e26e
authored
Aug 01, 2007
by
Bruce Momjian
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Done:
< * Allow buffered WAL writes and fsync
parent
4a78cdeb
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
4 additions
and
19 deletions
+4
-19
doc/TODO
doc/TODO
+2
-10
doc/src/FAQ/TODO.html
doc/src/FAQ/TODO.html
+2
-9
No files found.
doc/TODO
View file @
c441e26e
PostgreSQL TODO List
====================
Current maintainer: Bruce Momjian (bruce@momjian.us)
Last updated:
Tue Jul 17 20:15:52
EDT 2007
Last updated:
Wed Aug 1 19:13:20
EDT 2007
The most recent version of this document can be viewed at
http://www.postgresql.org/docs/faqs.TODO.html.
...
...
@@ -1330,15 +1330,7 @@ Write-Ahead Log
rotation to fsync again. One idea is to write the WAL to different
offsets that might reduce the rotational delay.
* Allow buffered WAL writes and fsync
Instead of guaranteeing recovery of all committed transactions, this
would provide improved performance by delaying WAL writes and fsync
so an abrupt operating system restart might lose a few seconds of
committed transactions but still be consistent. We could perhaps
remove the 'fsync' parameter (which results in an an inconsistent
database) in favor of this capability.
* -Allow buffered WAL writes and fsync
* Allow WAL logging to be turned off for a table, but the table
might be dropped or truncated during crash recovery [walcontrol]
...
...
doc/src/FAQ/TODO.html
View file @
c441e26e
...
...
@@ -8,7 +8,7 @@
<body
bgcolor=
"#FFFFFF"
text=
"#000000"
link=
"#FF0000"
vlink=
"#A00000"
alink=
"#0000FF"
>
<h1><a
name=
"section_1"
>
PostgreSQL TODO List
</a></h1>
<p>
Current maintainer: Bruce Momjian (
<a
href=
"mailto:bruce@momjian.us"
>
bruce@momjian.us
</a>
)
<br/>
Last updated:
Tue Jul 17 20:15:52
EDT 2007
Last updated:
Wed Aug 1 19:13:20
EDT 2007
</p>
<p>
The most recent version of this document can be viewed at
<br/>
<a
href=
"http://www.postgresql.org/docs/faqs.TODO.html"
>
http://www.postgresql.org/docs/faqs.TODO.html
</a>
.
...
...
@@ -1182,14 +1182,7 @@ first. There is also a developer's wiki at<br/>
rotation to fsync again. One idea is to write the WAL to different
offsets that might reduce the rotational delay.
</p>
</li><li>
Allow buffered WAL writes and fsync
<p>
Instead of guaranteeing recovery of all committed transactions, this
would provide improved performance by delaying WAL writes and fsync
so an abrupt operating system restart might lose a few seconds of
committed transactions but still be consistent. We could perhaps
remove the 'fsync' parameter (which results in an an inconsistent
database) in favor of this capability.
</p>
</li><li>
-
<em>
Allow buffered WAL writes and fsync
</em>
</li><li>
Allow WAL logging to be turned off for a table, but the table
might be dropped or truncated during crash recovery [
<a
href=
"http://momjian.postgresql.org/cgi-bin/pgtodo?walcontrol"
>
walcontrol
</a>
]
<p>
Allow tables to bypass WAL writes and just fsync() dirty pages on
...
...
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