|
10 | 10 | alink="#0000ff"> |
11 | 11 | <H1>Frequently Asked Questions (FAQ) for PostgreSQL</H1> |
12 | 12 |
|
13 | | -<P>Last updated: Wed Feb 2110:07:25 EST 2007</P> |
| 13 | +<P>Last updated: Wed Feb 2111:07:59 EST 2007</P> |
14 | 14 |
|
15 | 15 | <P>Current maintainer: Bruce Momjian (<Ahref= |
16 | 16 | "mailto:bruce@momjian.us">bruce@momjian.us</A>) |
@@ -584,16 +584,16 @@ <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 team makes only bug fixes in minor releases, |
588 | | - so, for example, upgrading from 7.4.8 to 7.4.9 does not require |
589 | | - a dump and restore; merely stop the database server, install |
590 | | - the updated binaries, and restart the server.</P> |
| 587 | +<P>The PostgreSQL team adds only bug fixes to minor releases. All |
| 588 | + users should upgrade to the most recent minor release as soon as it |
| 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 | + that upgrading.</P> |
591 | 593 |
|
592 | | -<P>All users should upgrade to the most recent minor release as soon |
593 | | - as it is available. While upgrades always have some risk, PostgreSQL |
594 | | - minor releases fix only common bugs to reduce the risk of upgrading. |
595 | | - The community considers<i>not</i> upgrading more risky that |
596 | | - upgrading.</P> |
| 594 | +<P>Upgrading to a minor release, e.g. 8.1.5 to 8.1.6, does not does |
| 595 | + not require a dump and restore; merely stop the database server, |
| 596 | + install the updated binaries, and restart the server.</P> |
597 | 597 |
|
598 | 598 | <P>Major releases (e.g. from 7.3 to 7.4) often change the internal |
599 | 599 | format of system tables and data files. These changes are often complex, |
|