From: | Ebin Jozer <ebinjozer(at)gmail(dot)com> |
---|---|
To: | Paul Smith <paul(at)pscs(dot)co(dot)uk> |
Cc: | Scott Ribe <scott_ribe(at)elevated-dev(dot)com>, pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Postgresql community edition upgrade |
Date: | 2022-10-13 09:42:57 |
Message-ID: | CAJuN1jj_QZTSwdHmA3SFC84EpXLm5mEC3awpg5PQaemY8CWB5Q@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Hi thanks for the response so far.
We have master and slave environment. So for upgrade we have upgrade first
in slave and then in master environment. Please confirm
On Thu, 13 Oct, 2022, 2:13 am Paul Smith, <paul(at)pscs(dot)co(dot)uk> wrote:
>
>
> On 12 October 2022 18:29:12 Scott Ribe <scott_ribe(at)elevated-dev(dot)com>
> wrote:
>
>> (I think even if you use link mode, it doesn't modify original catalog
>> files, so you can start the old one until you have started the new one. I'd
>> look for more info from someone more knowledgeable about this exact
>> process.)
>>
>
> Correct. I've had it go wrong with link mode. As long as you don't start
> the new cluster, the old one still works absolutely fine with a minor
> (documented) step.
>
> IIRC, the data files (in /data/base) are linked (and unchanged by the
> process). The control files, transaction logs, etc aren't, but the old
> control files are "disabled" to prevent accidental starting of the old
> cluster (it's easy to re-enable it)
>
> See (17) of the Usage notes
>
> https://www.postgresql.org/docs/current/pgupgrade.html
>
> Paul
>
>
> --
>
> Paul Smith Computer Services
> Tel: 01484 855800
> Vat No: GB 685 6987 53
>
> Sign up for news & updates <http://www.pscs.co.uk/go/subscribe>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Yogesh Mahajan | 2022-10-13 10:39:15 | Re: pgAdmin hangs while there is a long running process marked red |
Previous Message | Nikhil Ingale | 2022-10-13 06:28:24 | Re: Pg backup |