Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
summaryrefslogtreecommitdiff
path: root/doc/FAQ
diff options
context:
space:
mode:
authorBruce Momjian2007-03-20 17:43:57 +0000
committerBruce Momjian2007-03-20 17:43:57 +0000
commitc45fa5598b3bed81d564da592ce9ea67af18b313 (patch)
tree578acaeba917b2978ce2246d0a044c7eeb304f5e /doc/FAQ
parentd89b968319f57f80eee97de4337559d8fbcf2e8c (diff)
In FAQ, reference upgrade info via URL.
Diffstat (limited to 'doc/FAQ')
-rw-r--r--doc/FAQ34
1 files changed, 2 insertions, 32 deletions
diff --git a/doc/FAQ b/doc/FAQ
index 19870bf4a36..763ee5c5399 100644
--- a/doc/FAQ
+++ b/doc/FAQ
@@ -1,7 +1,7 @@
Frequently Asked Questions (FAQ) for PostgreSQL
- Last updated: Fri Feb 23 14:06:15 EST 2007
+ Last updated: Tue Mar 20 13:43:40 EDT 2007
Current maintainer: Bruce Momjian (bruce@momjian.us)
@@ -430,37 +430,7 @@
3.6) What is the upgrade process for PostgreSQL?
- PostgreSQL major releases include new features and occur roughly once
- every year. A major release is numbered by increasing either the first
- or second part of the version number, e.g. 8.1 to 8.2.
-
- Major releases usually change the internal format of system tables and
- data files. These changes are often complex, so we don't maintain
- backward compatibility for data files. A dump/reload of the database
- is required for major upgrades.
-
- Minor releases are numbered by increasing the third part of the
- version number, e.g. 8.1.5 to 8.1.6. The PostgreSQL team only adds bug
- fixes to minor releases. All 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 not upgrading riskier than upgrading.
- `
-
- Upgrading to a minor release does not does not require a dump and
- restore; merely stop the database server, install the updated
- binaries, and restart the server.
-
- 3.7) What computer hardware should I use?
-
- Because PC hardware is mostly compatible, people tend to believe that
- all PC hardware is of equal quality. It is not. ECC RAM, SCSI, and
- quality motherboards are more reliable and have better performance
- than less expensive hardware. PostgreSQL will run on almost any
- hardware, but if reliability and performance are important it is wise
- to research your hardware options thoroughly. Our email lists can be
- used to discuss hardware options and tradeoffs.
+ See http://www.postgresql.org/support/versioning.
_________________________________________________________________
Operational Questions