| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | pavan95 <pavan(dot)postgresdba(at)gmail(dot)com> |
| Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Upgrading from Postgresql 9.1 to 10 |
| Date: | 2018-02-14 15:04:28 |
| Message-ID: | CAKFQuwaxUq8MYAOjN1HpeF+-NJ2LzA7jLqHorR=cZnEHnokQgg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wednesday, February 14, 2018, David G. Johnston <
david(dot)g(dot)johnston(at)gmail(dot)com> wrote:
> On Wednesday, February 14, 2018, pavan95 <pavan(dot)postgresdba(at)gmail(dot)com>
> wrote:
>
>> Hi all,
>>
>> Is it possible to upgrade an existing postgresql 9.1 production system to
>> latest Postgres 10.0 version?
>>
>> The main requirement is to get rid of downtime. Please help me out!
>>
>
> Zero downtime is only possible by standing up a hot-standby then failing
> over to it. Same-server upgrade you can do via pg_upgrade but it does
> involve downtime. There are lots of material and options online, including
> the docs, for setting up hot-standby replication.
>
>
To clarify, you need to use logical replication here since the WAL format
is not usable across versions.
pg_upgrade is your simplest option if you can handle its downtime.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavan Teja | 2018-02-14 15:07:22 | Re: Upgrading from Postgresql 9.1 to 10 |
| Previous Message | Pavan Teja | 2018-02-14 14:51:03 | Re: Upgrading from Postgresql 9.1 to 10 |