|
1 | 1 |
|
2 | 2 | Frequently Asked Questions (FAQ) for PostgreSQL
|
3 | 3 |
|
4 |
| - Last updated: Wed Feb 2114:47:53 EST 2007 |
| 4 | + Last updated: Wed Feb 2117:54:05 EST 2007 |
5 | 5 |
|
6 | 6 | Current maintainer: Bruce Momjian (bruce@momjian.us)
|
7 | 7 |
|
|
431 | 431 | 3.6) What is the upgrade process for PostgreSQL?
|
432 | 432 |
|
433 | 433 | The PostgreSQL team only adds bug fixes to minor releases. All users
|
434 |
| - should upgrade to the most recent minor release as soon asit is |
435 |
| -available.While upgrades always have some risk, PostgreSQL minor |
436 |
| -releases fixonly frequently-encountered, security, and data |
437 |
| -corruption bugs, toreduce the risk of upgrading. The community |
438 |
| -considers not upgradingmore risky than upgrading. |
| 434 | + should upgrade to the most recent minor release as soon aspossible. |
| 435 | + While upgrades always have some risk, PostgreSQL minor releases fix |
| 436 | + only frequently-encountered, security, and data corruption bugs, to |
| 437 | + reduce the risk of upgrading. The community considers not upgrading |
| 438 | + more risky than upgrading. |
439 | 439 |
|
440 | 440 | Upgrading to a minor release, e.g. 8.1.5 to 8.1.6, does not does not
|
441 | 441 | require a dump and restore; merely stop the database server, install
|
|