|
10 | 10 | alink="#0000ff"> |
11 | 11 | <H1>Frequently Asked Questions (FAQ) for PostgreSQL</H1> |
12 | 12 |
|
13 | | -<P>Last updated:Tue Feb20 22:50:50 EST 2007</P> |
| 13 | +<P>Last updated:Wed Feb21 10:07:25 EST 2007</P> |
14 | 14 |
|
15 | 15 | <P>Current maintainer: Bruce Momjian (<Ahref= |
16 | 16 | "mailto:bruce@momjian.us">bruce@momjian.us</A>) |
@@ -589,11 +589,11 @@ <H3 id="item3.6">3.6) What is the upgrade process for PostgreSQL?</H3> |
589 | 589 | a dump and restore; merely stop the database server, install |
590 | 590 | the updated binaries, and restart the server.</P> |
591 | 591 |
|
592 | | -<P>All users should upgrade to the most recent minor release as |
593 | | -soonas it is available. Whileevery upgrade has some risk, |
594 | | -PostgreSQLminor releasesare designed tofix only common bugs |
595 | | -with the least risk.The community considers<i>not</i> upgrading |
596 | | -more risky thatupgrading.</P> |
| 592 | +<P>All users should upgrade to the most recent minor release as soon |
| 593 | + as it is available. Whileupgrades 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> |
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, |
|