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

Commitc45fa55

Browse files
committed
In FAQ, reference upgrade info via URL.
1 parentd89b968 commitc45fa55

File tree

2 files changed

+6
-64
lines changed

2 files changed

+6
-64
lines changed

‎doc/FAQ

Lines changed: 2 additions & 32 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:Fri Feb 23 14:06:15 EST 2007
4+
Last updated:Tue Mar 20 13:43:40 EDT 2007
55

66
Current maintainer: Bruce Momjian (bruce@momjian.us)
77

@@ -430,37 +430,7 @@
430430

431431
3.6) What is the upgrade process for PostgreSQL?
432432

433-
PostgreSQL major releases include new features and occur roughly once
434-
every year. A major release is numbered by increasing either the first
435-
or second part of the version number, e.g. 8.1 to 8.2.
436-
437-
Major releases usually change the internal format of system tables and
438-
data files. These changes are often complex, so we don't maintain
439-
backward compatibility for data files. A dump/reload of the database
440-
is required for major upgrades.
441-
442-
Minor releases are numbered by increasing the third part of the
443-
version number, e.g. 8.1.5 to 8.1.6. The PostgreSQL team only adds bug
444-
fixes to minor releases. All users should upgrade to the most recent
445-
minor release as soon as possible. While upgrades always have some
446-
risk, PostgreSQL minor releases fix only frequently-encountered,
447-
security, and data corruption bugs to reduce the risk of upgrading.
448-
The community considers not upgrading riskier than upgrading.
449-
`
450-
451-
Upgrading to a minor release does not does not require a dump and
452-
restore; merely stop the database server, install the updated
453-
binaries, and restart the server.
454-
455-
3.7) What computer hardware should I use?
456-
457-
Because PC hardware is mostly compatible, people tend to believe that
458-
all PC hardware is of equal quality. It is not. ECC RAM, SCSI, and
459-
quality motherboards are more reliable and have better performance
460-
than less expensive hardware. PostgreSQL will run on almost any
461-
hardware, but if reliability and performance are important it is wise
462-
to research your hardware options thoroughly. Our email lists can be
463-
used to discuss hardware options and tradeoffs.
433+
See http://www.postgresql.org/support/versioning.
464434
_________________________________________________________________
465435

466436
Operational Questions

‎doc/src/FAQ/FAQ.html

Lines changed: 4 additions & 32 deletions
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@
1010
alink="#0000ff">
1111
<H1>Frequently Asked Questions (FAQ) for PostgreSQL</H1>
1212

13-
<P>Last updated:Fri Feb 23 14:06:15 EST 2007</P>
13+
<P>Last updated:Tue Mar 20 13:43:40 EDT 2007</P>
1414

1515
<P>Current maintainer: Bruce Momjian (<Ahref=
1616
"mailto:bruce@momjian.us">bruce@momjian.us</A>)
@@ -584,37 +584,9 @@ <H3 id="item3.5">3.5) Why do I get <I>"Sorry, too many
584584

585585
<H3id="item3.6">3.6) What is the upgrade process for PostgreSQL?</H3>
586586

587-
<P>PostgreSQL major releases include new features and occur roughly
588-
once every year. A major release is numbered by increasing either
589-
the first or second part of the version number, e.g. 8.1 to 8.2.
590-
591-
<P>Major releases usually change the internal format of system tables
592-
and data files. These changes are often complex, so we don't maintain
593-
backward compatibility for data files. A dump/reload of the database
594-
is required for major upgrades.</P>
595-
596-
<P>Minor releases are numbered by increasing the third part of the
597-
version number, e.g. 8.1.5 to 8.1.6. The PostgreSQL team only adds
598-
bug fixes to minor releases. All users should upgrade to the most
599-
recent minor release as soon as possible. While upgrades always have
600-
some risk, PostgreSQL minor releases fix only frequently-encountered,
601-
security, and data corruption bugs to reduce the risk of upgrading.
602-
The community considers<i>not</i> upgrading riskier than
603-
upgrading.</P>
604-
`
605-
<P>Upgrading to a minor release does not does not require a dump and
606-
restore; merely stop the database server, install the updated binaries,
607-
and restart the server.</P>
608-
609-
<H3id="item3.7">3.7) What computer hardware should I use?</H3>
610-
611-
<P>Because PC hardware is mostly compatible, people tend to believe that
612-
all PC hardware is of equal quality. It is not. ECC RAM, SCSI, and
613-
quality motherboards are more reliable and have better performance than
614-
less expensive hardware. PostgreSQL will run on almost any hardware,
615-
but if reliability and performance are important it is wise to
616-
research your hardware options thoroughly. Our email lists can be used
617-
to discuss hardware options and tradeoffs.</P>
587+
<P>See<a
588+
href="http://www.postgresql.org/support/versioning">http://www.postgresql.org/support/versioning</a>.
589+
</P>
618590

619591
<HR>
620592

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp