Frequently Asked Questions (FAQ) for PostgreSQL

Last updated: Wed Feb 2114:47:53 EST 2007

Last updated: Wed Feb 2117:54:05 EST 2007

Current maintainer: Bruce Momjian (bruce@momjian.us)

3.6) What is the upgrade process for PostgreSQL?

The PostgreSQL team only adds bug fixes to minor releases. All users

should upgrade to the most recent minor release as soon asit is

available.While upgrades always have some risk, PostgreSQL minor

releases fixonly frequently-encountered, security, and data

corruption bugs, toreduce the risk of upgrading. The community

considers not upgradingmore risky than upgrading.

should upgrade to the most recent minor release as soon aspossible.

While upgrades always have some risk, PostgreSQL minor releases fix

only frequently-encountered, security, and data corruption bugs, to

reduce the risk of upgrading. The community 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

require a dump and restore; merely stop the database server, install

alink="#0000ff">

<H1>Frequently Asked Questions (FAQ) for PostgreSQL</H1>

<P>Last updated: Wed Feb 2114:47:53 EST 2007</P>

<P>Last updated: Wed Feb 2117:54:05 EST 2007</P>

<P>Current maintainer: Bruce Momjian (<Ahref=

"mailto:bruce@momjian.us">bruce@momjian.us</A>)

<H3id="item3.6">3.6) What is the upgrade process for PostgreSQL?</H3>

<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

users should upgrade to the most recent minor release as soon as

possible. While upgrades always have some risk, PostgreSQL minor

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>