Re: Postgresql community edition upgrade - Mailing list pgsql-admin

From Ebin Jozer
Subject Re: Postgresql community edition upgrade
Date
Msg-id CAJuN1jj_QZTSwdHmA3SFC84EpXLm5mEC3awpg5PQaemY8CWB5Q@mail.gmail.com
Whole thread Raw
In response to Re: Postgresql community edition upgrade  (Paul Smith <paul@pscs.co.uk>)
Responses Re: Postgresql community edition upgrade  (Scott Ribe <scott_ribe@elevated-dev.com>)
List 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@pscs.co.uk> wrote:


On 12 October 2022 18:29:12 Scott Ribe <scott_ribe@elevated-dev.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


Paul


--

Paul Smith Computer Services
Tel: 01484 855800
Vat No: GB 685 6987 53

pgsql-admin by date:

Previous
From: Nikhil Ingale
Date:
Subject: Re: Pg backup
Next
From: Matheus Alcantara
Date:
Subject: Re: pgAdmin hangs while there is a long running process marked red