database/postgres
database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-04-22 23:02:54 +03:00
Code

Update upgrade FAQ info.

Browse Source
This commit is contained in:
Bruce Momjian 2007-02-23 19:06:22 +00:00
parent b950596ffd
commit 1449e6f981
2 changed files with 40 additions and 28 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

34
doc/FAQ
View File

@ -1,7 +1,7 @@
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 @@
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
more risky than upgrading.
Upgrading to a minor release, e.g. 8.1.5 to 8.1.6, does not does not Major releases usually change the internal format of system tables and
require a dump and restore; merely stop the database server, install data files. These changes are often complex, so we don't maintain
the updated binaries, and restart the server. backward compatibility for data files. A dump/reload of the database
is required for major upgrades.
Major releases (e.g. from 7.3 to 7.4) often change the internal format Minor releases are numbered by increasing the third part of the
of system tables and data files. These changes are often complex, so version number, e.g. 8.1.5 to 8.1.6. The PostgreSQL team only adds bug
we don't maintain backward compatibility for data files. A dump/reload fixes to minor releases. All users should upgrade to the most recent
of the database is required for major upgrades. minor release as soon as possible. While upgrades always have some
risk, PostgreSQL minor releases fix only frequently-encountered,
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?

34
doc/src/FAQ/FAQ.html
View File

@ -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 @@
<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
<i>not</i> upgrading more risky than upgrading.</P>
<P>Upgrading to a minor release, e.g. 8.1.5 to 8.1.6, does not does <P>Major releases usually change the internal format of system tables
not require a dump and restore; merely stop the database server, and data files. These changes are often complex, so we don't maintain
install the updated binaries, and restart the server.</P> backward compatibility for data files. A dump/reload of the database
is required for major upgrades.</P>
<P>Major releases (e.g. from 7.3 to 7.4) often change the internal <P>Minor releases are numbered by increasing the third part of the
format of system tables and data files. These changes are often complex, version number, e.g. 8.1.5 to 8.1.6. The PostgreSQL team only adds
so we don't maintain backward compatibility for data files. A dump/reload bug fixes to minor releases. All users should upgrade to the most
of the database is required for major upgrades.</P> recent minor release as soon as possible. While upgrades always have
some risk, PostgreSQL minor releases fix only frequently-encountered,
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>