aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
-rw-r--r--doc/FAQ12
-rw-r--r--doc/src/FAQ/FAQ.html6
2 files changed, 9 insertions, 9 deletions
diff --git a/doc/FAQ b/doc/FAQ
index fd5f4e46b54..0097d276849 100644
--- a/doc/FAQ
+++ b/doc/FAQ
@@ -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
diff --git a/doc/src/FAQ/FAQ.html b/doc/src/FAQ/FAQ.html
index ecbe2b1624f..5ac1a0ec54b 100644
--- a/doc/src/FAQ/FAQ.html
+++ b/doc/src/FAQ/FAQ.html
@@ -10,7 +10,7 @@
alink="#0000ff">
<H1>Frequently Asked Questions (FAQ) for PostgreSQL</H1>
- <P>Last updated: Wed Feb 21 14:47:53 EST 2007</P>
+ <P>Last updated: Wed Feb 21 17:54:05 EST 2007</P>
<P>Current maintainer: Bruce Momjian (<A href=
"mailto:bruce@momjian.us">bruce@momjian.us</A>)
@@ -585,8 +585,8 @@
<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
- users should upgrade to the most recent minor release as soon as it
- is available. While upgrades always have some risk, PostgreSQL minor
+ users 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
<i>not</i> upgrading more risky than upgrading.</P>