Skip to content

P
Postgres FD Implementation
Commit 8c98fd6e authored by Bruce Momjian's avatar Bruce Momjian
Browse files
Options

Update upgrade wording.

parent 50c7e83c
Show whitespace changes
Inline Side-by-side
Showing with 9 additions and 9 deletions
doc/FAQ
View file @ 8c98fd6e
Frequently Asked Questions (FAQ) for PostgreSQL Frequently Asked Questions (FAQ) for PostgreSQL
Last updated: Wed Feb 21 14:47:53 EST 2007 Last updated: Wed Feb 21 17:54:05 EST 2007
Current maintainer: Bruce Momjian (bruce@momjian.us) Current maintainer: Bruce Momjian (bruce@momjian.us)
...@@ -431,11 +431,11 @@ ...@@ -431,11 +431,11 @@
3.6) What is the upgrade process for PostgreSQL? 3.6) What is the upgrade process for PostgreSQL?
The PostgreSQL team only adds 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 possible.
available. While upgrades always have some risk, PostgreSQL minor While upgrades always have some risk, PostgreSQL minor releases fix
releases fix only frequently-encountered, security, and data only frequently-encountered, security, and data corruption bugs, to
corruption bugs, to reduce the risk of upgrading. The community reduce the risk of upgrading. The community considers not upgrading
considers not upgrading more risky than 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
......
doc/src/FAQ/FAQ.html
View file @ 8c98fd6e
...@@ -10,7 +10,7 @@ ...@@ -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 14:47:53 EST 2007</P> <P>Last updated: Wed Feb 21 17:54:05 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>)
...@@ -585,8 +585,8 @@ ...@@ -585,8 +585,8 @@
<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 only adds 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
is available. While upgrades always have some risk, PostgreSQL minor possible. While upgrades always have some risk, PostgreSQL minor
releases fix only frequently-encountered, security, and data corruption releases fix only frequently-encountered, security, and data corruption
bugs, to reduce the risk of upgrading. The community considers bugs, to reduce the risk of upgrading. The community considers
<i>not</i> upgrading more risky than upgrading.</P> <i>not</i> upgrading more risky than upgrading.</P>
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment