Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: should we have a separate page that clearly defines what a minor release is and why it's a good idea to keep up with them?
- From: Peter Eisentraut <peter_e(at)gmx(dot)net>
- To: pgsql-docs(at)postgresql(dot)org
- Cc: Bruce Momjian <bruce(at)momjian(dot)us>, Magnus Hagander <magnus(at)hagander(dot)net>, Andrew Hammond <andrew(dot)george(dot)hammond(at)gmail(dot)com>
- Subject: Re: should we have a separate page that clearly defines what a minor release is and why it's a good idea to keep up with them?
- Date: Wed, 21 Feb 2007 16:42:43 +0100
Bruce Momjian wrote: > OK, the FAQ now has: > > <P>The PostgreSQL team makes only bug fixes in minor releases, I don't think there is a causality between the above and the below. > so, for example, upgrading from 7.4.8 to 7.4.9 does not require > a dump and restore; merely stop the database server, install > the updated binaries, and restart the server.</P> > <P>All users should upgrade to the most recent minor release as > soon as it is available. While upgrades always have some risk, > PostgreSQL minor releases fix only common bugs to reduce the risk of > upgrading. The community considers <i>not</i> upgrading more risky > that upgrading.</P> What is a "common bug"? -- Peter Eisentraut http://developer.postgresql.org/~petere/
- Follow-Ups:
- References:
- Prev by Date: Re: should we have a separate page that clearly defines what a minor release is and why it's a good idea to keep up with them?
- Next by Date: Re: should we have a separate page that clearly defines what a minor release is and why it's a good idea to keep up with them?
- Previous by thread: Re: should we have a separate page that clearly defines what a minor release is and why it's a good idea to keep up with them?
- Next by thread: Re: should we have a separate page that clearly defines what a minor release is and why it's a good idea to keep up with them?
- Indexes: