Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
From 8c98fd6e7fb508da1cf1ca0a932ba14191924044 Mon Sep 17 00:00:00 2001 From: Bruce Momjian Date: Wed, 21 Feb 2007 22:54:11 +0000 Subject: Update upgrade wording. --- doc/src/FAQ/FAQ.html | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'doc/src/FAQ/FAQ.html') 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">

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) @@ -585,8 +585,8 @@

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 + 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 not upgrading more risky than upgrading.

-- cgit v1.2.3