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

Commit8dd602e

Browse files
committed
Update mmap details:
< portability issues. Anonymous mmap is required to prevent I/O< overhead.> portability issues. Anonymous mmap (or mmap to /dev/zero) is required> to prevent I/O overhead.>> * Consider mmap()'ing files into a backend?>> Doing I/O to large tables would consume a lot of address space or> require frequent mapping/unmapping. Extending the file also causes> mapping problems that might require mapping only individual pages,> leading to thousands of mappings. Another problem is that there is no> way to _prevent_ I/O to disk from the dirty shared buffers so changes> could hit disk before WAL is written.
1 parentd9ab482 commit8dd602e

File tree

1 file changed

+12
-3
lines changed

1 file changed

+12
-3
lines changed

‎doc/TODO

Lines changed: 12 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ TODO list for PostgreSQL
66
Bracketed items "[]" have more detail.
77

88
Current maintainer:Bruce Momjian (pgman@candle.pha.pa.us)
9-
Last updated:Mon Nov 815:16:11 EST 2004
9+
Last updated:Mon Nov 822:57:34 EST 2004
1010

1111
The most recent version of this document can be viewed at the PostgreSQL web
1212
site, http://www.PostgreSQL.org.
@@ -815,8 +815,17 @@ Miscellaneous
815815
* Use mmap() rather than SYSV shared memory or to write WAL files (?) [mmap]
816816

817817
This would remove the requirement for SYSV SHM but would introduce
818-
portability issues. Anonymous mmap is required to prevent I/O
819-
overhead.
818+
portability issues. Anonymous mmap (or mmap to /dev/zero) is required
819+
to prevent I/O overhead.
820+
821+
* Consider mmap()'ing files into a backend?
822+
823+
Doing I/O to large tables would consume a lot of address space or
824+
require frequent mapping/unmapping. Extending the file also causes
825+
mapping problems that might require mapping only individual pages,
826+
leading to thousands of mappings. Another problem is that there is no
827+
way to _prevent_ I/O to disk from the dirty shared buffers so changes
828+
could hit disk before WAL is written.
820829

821830
* Add a script to ask system configuration questions and tune postgresql.conf
822831
* Use a phantom command counter for nested subtransactions to reduce

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp