|
|
|
|
@ -10,7 +10,7 @@ |
|
|
|
|
alink="#0000ff"> |
|
|
|
|
<H1>Frequently Asked Questions (FAQ) for PostgreSQL</H1> |
|
|
|
|
|
|
|
|
|
<P>Last updated: Tue Feb 20 22:50:50 EST 2007</P> |
|
|
|
|
<P>Last updated: Wed Feb 21 10:07:25 EST 2007</P> |
|
|
|
|
|
|
|
|
|
<P>Current maintainer: Bruce Momjian (<A href= |
|
|
|
|
"mailto:bruce@momjian.us">bruce@momjian.us</A>) |
|
|
|
|
@ -589,11 +589,11 @@ |
|
|
|
|
a dump and restore; merely stop the database server, install |
|
|
|
|
the updated binaries, and restart the server.</P> |
|
|
|
|
|
|
|
|
|
<P>All users should upgrade to the most recent minor release as |
|
|
|
|
soon as it is available. While every upgrade has some risk, |
|
|
|
|
PostgreSQL minor releases are designed to fix only common bugs |
|
|
|
|
with the least risk. The community considers <i>not</i> upgrading |
|
|
|
|
more risky that upgrading.</P> |
|
|
|
|
<P>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 common bugs to reduce the risk of upgrading. |
|
|
|
|
The community considers <i>not</i> upgrading more risky that |
|
|
|
|
upgrading.</P> |
|
|
|
|
|
|
|
|
|
<P>Major releases (e.g. from 7.3 to 7.4) often change the internal |
|
|
|
|
format of system tables and data files. These changes are often complex, |
|
|
|
|
|