mirrors/postgres
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Update FAQ about minor updates.

Browse Source
This commit is contained in:
Bruce Momjian 2007-02-21 19:48:02 +00:00
parent 9bc6af8026
commit 526b1d6979
2 changed files with 10 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
doc/FAQ
View File

@ -1,7 +1,7 @@
Frequently Asked Questions (FAQ) for PostgreSQL Frequently Asked Questions (FAQ) for PostgreSQL
Last updated: Wed Feb 21 11:08:51 EST 2007 Last updated: Wed Feb 21 14:47:53 EST 2007
Current maintainer: Bruce Momjian (bruce@momjian.us) Current maintainer: Bruce Momjian (bruce@momjian.us)
@ -430,12 +430,12 @@
3.6) What is the upgrade process for PostgreSQL? 3.6) What is the upgrade process for PostgreSQL?
The PostgreSQL team adds only bug fixes to minor releases. All users 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 should upgrade to the most recent minor release as soon as it is
available. While upgrades always have some risk, PostgreSQL minor available. While upgrades always have some risk, PostgreSQL minor
releases fix only frequently-encountered bugs to reduce the risk of releases fix only frequently-encountered, security, and data
upgrading. The community considers not upgrading more risky than corruption bugs, to reduce the risk of upgrading. The community
upgrading. considers not upgrading more risky than upgrading.
Upgrading to a minor release, e.g. 8.1.5 to 8.1.6, does not does not 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, install require a dump and restore; merely stop the database server, install

10
doc/src/FAQ/FAQ.html
View File

@ -10,7 +10,7 @@
alink="#0000ff"> alink="#0000ff">
<H1>Frequently Asked Questions (FAQ) for PostgreSQL</H1> <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= <P>Current maintainer: Bruce Momjian (<A href=
"mailto:bruce@momjian.us">bruce@momjian.us</A>) "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> <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 users should upgrade to the most recent minor release as soon as it
is available. While upgrades always have some risk, PostgreSQL minor is available. While upgrades always have some risk, PostgreSQL minor
releases fix only frequently-encountered bugs to reduce the risk of releases fix only frequently-encountered, security, and data corruption
upgrading. The community considers <i>not</i> upgrading more risky bugs, to reduce the risk of upgrading. The community considers
than upgrading.</P> <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 <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, not require a dump and restore; merely stop the database server,