Skip to content

Commit 1449e6f

Browse files
bmomjianbmomjian
committed
Update upgrade FAQ info.
1 parent b950596 commit 1449e6f

File tree

2 files changed

+44
-32
lines changed

2 files changed

+44
-32
lines changed

‎doc/FAQ

+22-16
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11

22
Frequently Asked Questions (FAQ) for PostgreSQL
33

4-
Last updated: Wed Feb 21 17:54:05 EST 2007
4+
Last updated: Fri Feb 23 14:06:15 EST 2007
55

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

@@ -430,21 +430,27 @@
430430

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

433-
The PostgreSQL team only adds bug fixes to minor releases. All users
434-
should upgrade to the most recent minor release as soon as possible.
435-
While upgrades always have some risk, PostgreSQL minor releases fix
436-
only frequently-encountered, security, and data corruption bugs, to
437-
reduce the risk of upgrading. The community considers not upgrading
438-
more risky than upgrading.
439-
440-
Upgrading to a minor release, e.g. 8.1.5 to 8.1.6, does not does not
441-
require a dump and restore; merely stop the database server, install
442-
the updated binaries, and restart the server.
443-
444-
Major releases (e.g. from 7.3 to 7.4) often change the internal format
445-
of system tables and data files. These changes are often complex, so
446-
we don't maintain backward compatibility for data files. A dump/reload
447-
of the database is required for major upgrades.
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.
448454

449455
3.7) What computer hardware should I use?
450456

‎doc/src/FAQ/FAQ.html

+22-16
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: Wed Feb 21 17:54:05 EST 2007</P>
13+
<P>Last updated: Fri Feb 23 14:06:15 EST 2007</P>
1414

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

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

587-
<P>The PostgreSQL team only adds bug fixes to minor releases. All
588-
users should upgrade to the most recent minor release as soon as
589-
possible. While upgrades always have some risk, PostgreSQL minor
590-
releases fix only frequently-encountered, security, and data corruption
591-
bugs, to reduce the risk of upgrading. The community considers
592-
<i>not</i> upgrading more risky than upgrading.</P>
593-
594-
<P>Upgrading to a minor release, e.g. 8.1.5 to 8.1.6, does not does
595-
not require a dump and restore; merely stop the database server,
596-
install the updated binaries, and restart the server.</P>
597-
598-
<P>Major releases (e.g. from 7.3 to 7.4) often change the internal
599-
format of system tables and data files. These changes are often complex,
600-
so we don't maintain backward compatibility for data files. A dump/reload
601-
of the database is required for major upgrades.</P>
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>
602608

603609
<H3 id="item3.7">3.7) What computer hardware should I use?</H3>
604610

0 commit comments

Comments
 (0)