Skip to content
Snippets Groups Projects
Commit 1449e6f9 authored by Bruce Momjian's avatar Bruce Momjian
Browse files

Update upgrade FAQ info.

parent b950596f
No related branches found
No related tags found
No related merge requests found
Show whitespace changes
Inline Side-by-side
doc/FAQ
+ 22
− 16
View file @ 1449e6f9
Frequently Asked Questions (FAQ) for PostgreSQL Frequently Asked Questions (FAQ) for PostgreSQL
Last updated: Wed Feb 21 17:54:05 EST 2007 Last updated: Fri Feb 23 14:06:15 EST 2007
Current maintainer: Bruce Momjian (bruce@momjian.us) Current maintainer: Bruce Momjian (bruce@momjian.us)
...@@ -430,21 +430,27 @@ ...@@ -430,21 +430,27 @@
3.6) What is the upgrade process for PostgreSQL? 3.6) What is the upgrade process for PostgreSQL?
The PostgreSQL team only adds bug fixes to minor releases. All users PostgreSQL major releases include new features and occur roughly once
should upgrade to the most recent minor release as soon as possible. every year. A major release is numbered by increasing either the first
While upgrades always have some risk, PostgreSQL minor releases fix or second part of the version number, e.g. 8.1 to 8.2.
only frequently-encountered, security, and data corruption bugs, to
reduce the risk of upgrading. The community considers not upgrading Major releases usually change the internal format of system tables and
more risky than upgrading. data files. These changes are often complex, so we don't maintain
backward compatibility for data files. A dump/reload of the database
Upgrading to a minor release, e.g. 8.1.5 to 8.1.6, does not does not is required for major upgrades.
require a dump and restore; merely stop the database server, install
the updated binaries, and restart the server. Minor releases are numbered by increasing the third part of the
version number, e.g. 8.1.5 to 8.1.6. The PostgreSQL team only adds bug
Major releases (e.g. from 7.3 to 7.4) often change the internal format fixes to minor releases. All users should upgrade to the most recent
of system tables and data files. These changes are often complex, so minor release as soon as possible. While upgrades always have some
we don't maintain backward compatibility for data files. A dump/reload risk, PostgreSQL minor releases fix only frequently-encountered,
of the database is required for major upgrades. security, and data corruption bugs to reduce the risk of upgrading.
The community considers not upgrading riskier than upgrading.
`
Upgrading to a minor release does not does not require a dump and
restore; merely stop the database server, install the updated
binaries, and restart the server.
3.7) What computer hardware should I use? 3.7) What computer hardware should I use?
......
doc/src/FAQ/FAQ.html
+ 22
− 16
View file @ 1449e6f9
...@@ -10,7 +10,7 @@ ...@@ -10,7 +10,7 @@
alink="#0000ff"> alink="#0000ff">
<H1>Frequently Asked Questions (FAQ) for PostgreSQL</H1> <H1>Frequently Asked Questions (FAQ) for PostgreSQL</H1>
<P>Last updated: Wed Feb 21 17:54:05 EST 2007</P> <P>Last updated: Fri Feb 23 14:06:15 EST 2007</P>
<P>Current maintainer: Bruce Momjian (<A href= <P>Current maintainer: Bruce Momjian (<A href=
"mailto:bruce@momjian.us">bruce@momjian.us</A>) "mailto:bruce@momjian.us">bruce@momjian.us</A>)
...@@ -584,21 +584,27 @@ ...@@ -584,21 +584,27 @@
<H3 id="item3.6">3.6) What is the upgrade process for PostgreSQL?</H3> <H3 id="item3.6">3.6) What is the upgrade process for PostgreSQL?</H3>
<P>The PostgreSQL team only adds bug fixes to minor releases. All <P>PostgreSQL major releases include new features and occur roughly
users should upgrade to the most recent minor release as soon as once every year. A major release is numbered by increasing either
possible. While upgrades always have some risk, PostgreSQL minor the first or second part of the version number, e.g. 8.1 to 8.2.
releases fix only frequently-encountered, security, and data corruption
bugs, to reduce the risk of upgrading. The community considers <P>Major releases usually change the internal format of system tables
<i>not</i> upgrading more risky than upgrading.</P> and data files. These changes are often complex, so we don't maintain
backward compatibility for data files. A dump/reload of the database
<P>Upgrading to a minor release, e.g. 8.1.5 to 8.1.6, does not does is required for major upgrades.</P>
not require a dump and restore; merely stop the database server,
install the updated binaries, and restart the server.</P> <P>Minor releases are numbered by increasing the third part of the
version number, e.g. 8.1.5 to 8.1.6. The PostgreSQL team only adds
<P>Major releases (e.g. from 7.3 to 7.4) often change the internal bug fixes to minor releases. All users should upgrade to the most
format of system tables and data files. These changes are often complex, recent minor release as soon as possible. While upgrades always have
so we don't maintain backward compatibility for data files. A dump/reload some risk, PostgreSQL minor releases fix only frequently-encountered,
of the database is required for major upgrades.</P> security, and data corruption bugs to reduce the risk of upgrading.
The community considers <i>not</i> upgrading riskier than
upgrading.</P>
`
<P>Upgrading to a minor release does not does not require a dump and
restore; merely stop the database server, install the updated binaries,
and restart the server.</P>
<H3 id="item3.7">3.7) What computer hardware should I use?</H3> <H3 id="item3.7">3.7) What computer hardware should I use?</H3>
......
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment