diff options
| author | Bruce Momjian | 2007-02-21 22:54:11 +0000 |
|---|---|---|
| committer | Bruce Momjian | 2007-02-21 22:54:11 +0000 |
| commit | 8c98fd6e7fb508da1cf1ca0a932ba14191924044 (patch) | |
| tree | 99172e71885fb5060807a233902129127ee9d7a9 /doc/FAQ | |
| parent | 50c7e83cd71098df861e5d19159b82b0d9938a31 (diff) | |
Update upgrade wording.
Diffstat (limited to 'doc/FAQ')
| -rw-r--r-- | doc/FAQ | 12 |
1 files changed, 6 insertions, 6 deletions
@@ -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 |