|
|
|
@ -1,7 +1,7 @@ |
|
|
|
|
|
|
|
|
|
Frequently Asked Questions (FAQ) for PostgreSQL |
|
|
|
|
|
|
|
|
|
Last updated: Wed Feb 21 14:47:53 EST 2007 |
|
|
|
|
Last updated: Wed Feb 21 17:54:05 EST 2007 |
|
|
|
|
|
|
|
|
|
Current maintainer: Bruce Momjian (bruce@momjian.us) |
|
|
|
|
|
|
|
|
@ -431,11 +431,11 @@ |
|
|
|
|
3.6) What is the upgrade process for PostgreSQL? |
|
|
|
|
|
|
|
|
|
The PostgreSQL team only adds bug fixes to minor releases. All users |
|
|
|
|
should upgrade to the most recent minor release as soon as it is |
|
|
|
|
available. 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 more risky than upgrading. |
|
|
|
|
should upgrade to the most 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 not upgrading |
|
|
|
|
more risky than upgrading. |
|
|
|
|
|
|
|
|
|
Upgrading to a minor release, e.g. 8.1.5 to 8.1.6, does not does not |
|
|
|
|
require a dump and restore; merely stop the database server, install |
|
|
|
|