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

Commit8d1c1d4

Browse files
committed
Update fsync FAQ item.
1 parentc86fac2 commit8d1c1d4

File tree

2 files changed

+19
-44
lines changed

2 files changed

+19
-44
lines changed

‎doc/FAQ

Lines changed: 8 additions & 21 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11

22
Frequently Asked Questions (FAQ) for PostgreSQL
33

4-
Last updated: Mon Jun 1016:44:55 EDT 2002
4+
Last updated: Mon Jun 1022:22:31 EDT 2002
55

66
Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us)
77

@@ -323,29 +323,16 @@
323323
reduce lock contention.
324324

325325
Performance
326-
PostgreSQL runs in two modes. Normal fsync mode flushes every
327-
completed transaction to disk, guaranteeing that if the OS
328-
crashes or loses power in the next few seconds, all your data
329-
is safely stored on disk. In this mode, we are slower than most
330-
commercial databases, partly because few of them do such
331-
conservative flushing to disk in their default modes. In
332-
no-fsync mode, we are usually faster than commercial databases,
333-
though in this mode, an OS crash could cause data corruption.
334-
We are working to provide an intermediate mode that suffers
335-
less performance overhead than full fsync mode, and will allow
336-
data integrity within 30 seconds of an OS crash.
326+
PostgreSQL has performance similar to other commercial and open
327+
source databases. it is faster for some things, slower for
328+
others.
337329
In comparison to MySQL or leaner database systems, we are
338330
slower on inserts/updates because we have transaction overhead.
339331
Of course, MySQL does not have any of the features mentioned in
340-
the Features section above. We are built for flexibility and
341-
features, though we continue to improve performance through
342-
profiling and source code analysis. There is an interesting Web
343-
page comparing PostgreSQL to MySQL at
344-
http://openacs.org/why-not-mysql.html
345-
We handle each user connection by creating a Unix process.
346-
Backend processes share data buffers and locking information.
347-
With multiple CPUs, multiple backends can easily run on
348-
different CPUs.
332+
the Features section above. We are built for reliability and
333+
features, though we continue to improve performance in every
334+
release. There is an interesting Web page comparing PostgreSQL
335+
to MySQL at http://openacs.org/why-not-mysql.html
349336

350337
Reliability
351338
We realize that a DBMS must be reliable, or it is worthless. We

‎doc/src/FAQ/FAQ.html

Lines changed: 11 additions & 23 deletions
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@
1414
alink="#0000ff">
1515
<H1>Frequently Asked Questions (FAQ) for PostgreSQL</H1>
1616

17-
<P>Last updated: Mon Jun 1016:44:55 EDT 2002</P>
17+
<P>Last updated: Mon Jun 1022:22:31 EDT 2002</P>
1818

1919
<P>Current maintainer: Bruce Momjian (<Ahref=
2020
"mailto:pgman@candle.pha.pa.us">pgman@candle.pha.pa.us</A>)<BR>
@@ -425,32 +425,20 @@ <H4><A name="1.14">1.14</A>) How does PostgreSQL compare to other
425425

426426
<DT><B>Performance</B></DT>
427427

428-
<DD>PostgreSQL runs in two modes. Normal<I>fsync</I> mode
429-
flushes every completed transaction to disk, guaranteeing that if
430-
the OS crashes or loses power in the next few seconds, all your
431-
data is safely stored on disk. In this mode, we are slower than
432-
most commercial databases, partly because few of them do such
433-
conservative flushing to disk in their default modes. In
434-
<I>no-fsync</I> mode, we are usually faster than commercial
435-
databases, though in this mode, an OS crash could cause data
436-
corruption. We are working to provide an intermediate mode that
437-
suffers less performance overhead than full fsync mode, and will
438-
allow data integrity within 30 seconds of an OS crash.<BR>
428+
<DD>PostgreSQL has performance similar to other commercial and
429+
open source databases. it is faster for some things, slower for
430+
others.
439431
<BR>
440-
In comparison to MySQL or leaner database systems, we are slower
432+
In comparison to MySQL or leaner database systems, we are slower
441433
on inserts/updates because we have transaction overhead. Of
442434
course, MySQL does not have any of the features mentioned in the
443-
<I>Features</I> section above. We are built for flexibility and
444-
features, though we continue to improve performance through
445-
profiling and source code analysis. There is an interesting Web
446-
page comparing PostgreSQL to MySQL at<Ahref=
447-
"http://openacs.org/why-not-mysql.html">http://openacs.org/why-not-mysql.html</A><BR>
435+
<I>Features</I> section above. We are built for reliability and
436+
features, though we continue to improve performance in every
437+
release. There is an interesting Web page comparing PostgreSQL to
438+
MySQL at<Ahref= "http://openacs.org/why-not-mysql.html">
439+
440+
http://openacs.org/why-not-mysql.html</A><BR>
448441

449-
<BR>
450-
We handle each user connection by creating a Unix process.
451-
Backend processes share data buffers and locking information.
452-
With multiple CPUs, multiple backends can easily run on different
453-
CPUs.<BR>
454442
<BR>
455443
</DD>
456444

0 commit comments

Comments
 (0)
[8]ページ先頭
©2009-2025 Movatter.jp