| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Pawan Sharma <pawanpg0963(at)gmail(dot)com> |
| Cc: | "pgsql-general(at)postgresql(dot)org >> PG-General Mailing List" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Release upgarde failure |
| Date: | 2018-03-02 15:03:44 |
| Message-ID: | CAKFQuwZr9cBo3Zqh7PcAeGrANUgDfhUz25LJhyWgO794djuw4A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Fri, Mar 2, 2018 at 7:55 AM, Pawan Sharma <pawanpg0963(at)gmail(dot)com> wrote:
> Hi All,
>
> Please let me know the reasons of release upgrade failure in PostgreSQL
> which you guys faced while doing it.
>
> Example: 9.5.1 to 9.5.2
>
>
It is highly unlikely that you will encounter a failure when upgrading to
a new minor release.
Major releases are a different matter though usually the upgrade happens
just fine but if you aren't careful to also update your applications they
could start working if you are using features that have changed
incompatibly, though we do try to minimize that.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2018-03-02 16:21:44 | Re: jsonb_array_length: ERROR: 22023: cannot get array length of a scalar |
| Previous Message | Pawan Sharma | 2018-03-02 14:55:03 | Release upgarde failure |