|
|
|
|
@ -10,7 +10,7 @@ |
|
|
|
|
alink="#0000ff"> |
|
|
|
|
<H1>Frequently Asked Questions (FAQ) for PostgreSQL</H1> |
|
|
|
|
|
|
|
|
|
<P>Last updated: Wed Feb 21 11:08:51 EST 2007</P> |
|
|
|
|
<P>Last updated: Wed Feb 21 14:47:53 EST 2007</P> |
|
|
|
|
|
|
|
|
|
<P>Current maintainer: Bruce Momjian (<A href= |
|
|
|
|
"mailto:bruce@momjian.us">bruce@momjian.us</A>) |
|
|
|
|
@ -584,12 +584,12 @@ |
|
|
|
|
|
|
|
|
|
<H3 id="item3.6">3.6) What is the upgrade process for PostgreSQL?</H3> |
|
|
|
|
|
|
|
|
|
<P>The PostgreSQL team adds only bug fixes to minor releases. All |
|
|
|
|
<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 |
|
|
|
|
releases fix only frequently-encountered bugs to reduce the risk of |
|
|
|
|
upgrading. The community considers <i>not</i> upgrading more risky |
|
|
|
|
than upgrading.</P> |
|
|
|
|
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> |
|
|
|
|
|
|
|
|
|
<P>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, |
|
|
|
|
|