From: | Matheus de Oliveira <matioli(dot)matheus(at)gmail(dot)com> |
---|---|
To: | jlrando <jose(dot)luis(dot)rando(dot)calvo(at)ericsson(dot)com> |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: Re: Hot standby 9.2.6 -> 9.2.6 PANIC: WAL contains references to invalid pages |
Date: | 2014-06-09 18:58:17 |
Message-ID: | CAJghg4+p2aJaZEg3-awKd0Yd15HR5VMrzpKdJoV3yyVS_Mn1wA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-hackers |
On Mon, Jun 9, 2014 at 11:10 AM, jlrando <jose(dot)luis(dot)rando(dot)calvo(at)ericsson(dot)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/
--
Matheus de Oliveira
Analista de Banco de Dados
Dextra Sistemas - MPS.Br nível F!
www.dextra.com.br/postgres
From | Date | Subject | |
---|---|---|---|
Next Message | geoff | 2014-06-09 19:16:09 | BUG #10587: ERROR: variable not found in subplan target list |
Previous Message | Jeff Janes | 2014-06-09 15:57:35 | Re: Many processes blocked at ProcArrayLock! |
From | Date | Subject | |
---|---|---|---|
Next Message | Kevin Grittner | 2014-06-09 19:04:04 | Re: Inaccuracy in VACUUM's tuple count estimates |
Previous Message | Alvaro Herrera | 2014-06-09 18:55:54 | Re: Inaccuracy in VACUUM's tuple count estimates |