aboutsummaryrefslogtreecommitdiff
path: root/doc/FAQ
diff options
context:
space:
mode:
authorBruce Momjian <bruce@momjian.us>2007-02-21 19:48:02 +0000
committerBruce Momjian <bruce@momjian.us>2007-02-21 19:48:02 +0000
commit526b1d697985642ee42959d65903f1d504ae57b0 (patch)
treea439f00c0aa9bf6340b4a08a3b4d11c7894721f6 /doc/FAQ
parent9bc6af8026c5b3a71f802253555b364e1e78ad27 (diff)
downloadpostgresql-526b1d697985642ee42959d65903f1d504ae57b0.tar.gz
postgresql-526b1d697985642ee42959d65903f1d504ae57b0.zip
Update FAQ about minor updates.
Diffstat (limited to 'doc/FAQ')
-rw-r--r--doc/FAQ10
1 files changed, 5 insertions, 5 deletions
diff --git a/doc/FAQ b/doc/FAQ
index 5aac1867b7d..fd5f4e46b54 100644
--- a/doc/FAQ
+++ b/doc/FAQ
@@ -1,7 +1,7 @@
Frequently Asked Questions (FAQ) for PostgreSQL
- Last updated: Wed Feb 21 11:08:51 EST 2007
+ Last updated: Wed Feb 21 14:47:53 EST 2007
Current maintainer: Bruce Momjian (bruce@momjian.us)
@@ -430,12 +430,12 @@
3.6) What is the upgrade process for PostgreSQL?
- The PostgreSQL team adds only bug fixes to minor releases. All users
+ 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 bugs to reduce the risk of
- upgrading. The community considers not upgrading more risky than
- upgrading.
+ 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