On Tue, Jun 10, 2014 at 3:58 AM, Matheus de Oliveira
<matioli.matheus@gmail.com> wrote:
>
> On Mon, Jun 9, 2014 at 11:10 AM, jlrando
> <jose.luis.rando.calvo@ericsson.com> wrote:
>>
>> Perform an upgrade of this DB will require a
>> lot of time because the only certified DB version for this application is
>> 9.2.6.
>
>
> This simple makes no sense for PG release versioning schema/policy, see [1].
>
> Following schema X.Y.Z of a PG release, you may "certifies" an application
> to work on version X.Y only, the Z number means the release (bug-fix/patch
> basically), and you should **always** be using the most higher Z for your
> X.Y version (in the case of 9.2, you should be using 9.2.8 already, no
> excuses). In summary, you can always upgrade from Z to Z+1 without
> compatibility issues. Of course, read the release notes to check if there is
> some maintenance needed after the upgrade.
>
> [1] http://www.postgresql.org/support/versioning/
The same major versions (X.Y releases) are guaranteed to be
disk-compatible and new minor releases only contain bug fixes. So
updating is only a matter of installing the new binaries and then
restart the server. By updating always to the latest available version
you protect as well your application from the latest bugs found.
--
Michael