Re: Postgresql community edition upgrade

From: Paul Smith <paul(at)pscs(dot)co(dot)uk>
To: Scott Ribe <scott_ribe(at)elevated-dev(dot)com>, Ebin Jozer <ebinjozer(at)gmail(dot)com>
Cc: "pgsql-admin" <pgsql-admin(at)lists(dot)postgresql(dot)org>
Subject: Re: Postgresql community edition upgrade
Date: 2022-10-12 20:38:11
Message-ID: 183cdeb4338.2923.9bfe8bcc586ac955e423c0e3d5444448@pscs.co.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

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 at http://www.pscs.co.uk/go/subscribe

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Shaozhong SHI 2022-10-12 21:04:40 pgAdmin hangs while there is a long running process marked red
Previous Message Laurenz Albe 2022-10-12 20:21:17 Re: Postgresql community edition upgrade