|
10 | 10 | alink="#0000ff"> |
11 | 11 | <H1>Frequently Asked Questions (FAQ) for PostgreSQL</H1> |
12 | 12 |
|
13 | | - <P>Last updated: Fri Feb 23 14:06:15 EST 2007</P> |
| 13 | + <P>Last updated: Tue Mar 20 13:43:40 EDT 2007</P> |
14 | 14 |
|
15 | 15 | <P>Current maintainer: Bruce Momjian (<A href= |
16 | 16 | "mailto:bruce@momjian.us">bruce@momjian.us</A>) |
@@ -584,37 +584,9 @@ <H3 id="item3.5">3.5) Why do I get <I>"Sorry, too many |
584 | 584 |
|
585 | 585 | <H3 id="item3.6">3.6) What is the upgrade process for PostgreSQL?</H3> |
586 | 586 |
|
587 | | - <P>PostgreSQL major releases include new features and occur roughly |
588 | | - once every year. A major release is numbered by increasing either |
589 | | - the first or second part of the version number, e.g. 8.1 to 8.2. |
590 | | - |
591 | | - <P>Major releases usually change the internal format of system tables |
592 | | - and data files. These changes are often complex, so we don't maintain |
593 | | - backward compatibility for data files. A dump/reload of the database |
594 | | - is required for major upgrades.</P> |
595 | | - |
596 | | - <P>Minor releases are numbered by increasing the third part of the |
597 | | - version number, e.g. 8.1.5 to 8.1.6. The PostgreSQL team only adds |
598 | | - bug fixes to minor releases. All users should upgrade to the most |
599 | | - recent minor release as soon as possible. While upgrades always have |
600 | | - some risk, PostgreSQL minor releases fix only frequently-encountered, |
601 | | - security, and data corruption bugs to reduce the risk of upgrading. |
602 | | - The community considers <i>not</i> upgrading riskier than |
603 | | - upgrading.</P> |
604 | | -` |
605 | | - <P>Upgrading to a minor release does not does not require a dump and |
606 | | - restore; merely stop the database server, install the updated binaries, |
607 | | - and restart the server.</P> |
608 | | - |
609 | | - <H3 id="item3.7">3.7) What computer hardware should I use?</H3> |
610 | | - |
611 | | - <P>Because PC hardware is mostly compatible, people tend to believe that |
612 | | - all PC hardware is of equal quality. It is not. ECC RAM, SCSI, and |
613 | | - quality motherboards are more reliable and have better performance than |
614 | | - less expensive hardware. PostgreSQL will run on almost any hardware, |
615 | | - but if reliability and performance are important it is wise to |
616 | | - research your hardware options thoroughly. Our email lists can be used |
617 | | - to discuss hardware options and tradeoffs.</P> |
| 587 | + <P>See <a |
| 588 | + href="http://www.postgresql.org/support/versioning">http://www.postgresql.org/support/versioning</a>. |
| 589 | + </P> |
618 | 590 |
|
619 | 591 | <HR> |
620 | 592 |
|
|
0 commit comments