|
10 | 10 | alink="#0000ff"> |
11 | 11 | <H1>Frequently Asked Questions (FAQ) for PostgreSQL</H1> |
12 | 12 |
|
13 | | -<P>Last updated: Wed Feb 2111:08:51 EST 2007</P> |
| 13 | +<P>Last updated: Wed Feb 2114:47:53 EST 2007</P> |
14 | 14 |
|
15 | 15 | <P>Current maintainer: Bruce Momjian (<Ahref= |
16 | 16 | "mailto:bruce@momjian.us">bruce@momjian.us</A>) |
@@ -584,12 +584,12 @@ <H3 id="item3.5">3.5) Why do I get <I>"Sorry, too many |
584 | 584 |
|
585 | 585 | <H3id="item3.6">3.6) What is the upgrade process for PostgreSQL?</H3> |
586 | 586 |
|
587 | | -<P>The PostgreSQL teamaddsonly bug fixes to minor releases. All |
| 587 | +<P>The PostgreSQL team only adds bug fixes to minor releases. All |
588 | 588 | users should upgrade to the most recent minor release as soon as it |
589 | 589 | is available. While upgrades always have some risk, PostgreSQL minor |
590 | | - releases fix only frequently-encountered bugs to reduce the risk of |
591 | | -upgrading. The community considers<i>not</i> upgrading more risky |
592 | | - than upgrading.</P> |
| 590 | + releases fix only frequently-encountered, security, and data corruption |
| 591 | +bugs, to reduce the risk of upgrading. The community considers |
| 592 | +<i>not</i> upgrading more riskythan upgrading.</P> |
593 | 593 |
|
594 | 594 | <P>Upgrading to a minor release, e.g. 8.1.5 to 8.1.6, does not does |
595 | 595 | not require a dump and restore; merely stop the database server, |
|