pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Paul Smith <paul@pscs.co.uk>
To: Scott Ribe <scott_ribe@elevated-dev.com>
To: Ebin Jozer <ebinjozer@gmail.com>
Cc: pgsql-admin <pgsql-admin@lists.postgresql.org>
Subject: Re: Postgresql community edition upgrade
Date: Wed, 12 Oct 2022 21:38:11 +0100
Message-ID: <183cdeb4338.2923.9bfe8bcc586ac955e423c0e3d5444448@pscs.co.uk> (raw)
In-Reply-To: <9571D051-5B4F-45FB-A52B-9D84C601B7DC@elevated-dev.com>
References: <CAJuN1jj9=x5FPUypuCGntG82mbZQbW-XOWgbg+H97MrwZ20wLA@mail.gmail.com>
	<7ce8278e-f943-74d4-ca73-cbf9e422f784@jakobs.com>
	<CAJuN1jiQ+nUMkay00SSS-axrOBrCL4QoYhRp6sWWdS_S4OHwRg@mail.gmail.com>
	<9571D051-5B4F-45FB-A52B-9D84C601B7DC@elevated-dev.com>



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

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

view thread (8+ messages)  latest in thread

Message-ID: <183cdeb4338.2923.9bfe8bcc586ac955e423c0e3d5444448@pscs.co.uk>
Permalink:  ../183cdeb4338.2923.9bfe8bcc586ac955e423c0e3d5444448@pscs.co.uk/
Also on:    postgresql.org/message-id/183cdeb4338.2923.9bfe8bcc586ac955e423c0e3d5444448@pscs.co.uk

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: paul@pscs.co.uk, scott_ribe@elevated-dev.com, ebinjozer@gmail.com, pgsql-admin@lists.postgresql.org
  Subject: Re: Postgresql community edition upgrade
  In-Reply-To: <183cdeb4338.2923.9bfe8bcc586ac955e423c0e3d5444448@pscs.co.uk>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox