Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oiiZg-0003oG-NO for pgsql-admin@arkaria.postgresql.org; Wed, 12 Oct 2022 20:43:33 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1oiiZf-0006OB-Hm for pgsql-admin@arkaria.postgresql.org; Wed, 12 Oct 2022 20:43:31 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oiiZf-0006NZ-4X for pgsql-admin@lists.postgresql.org; Wed, 12 Oct 2022 20:43:31 +0000 Received: from mail.pscs.co.uk ([178.159.9.185]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oiiZc-0001VG-7z for pgsql-admin@lists.postgresql.org; Wed, 12 Oct 2022 20:43:30 +0000 Authentication-Results: mail.pscs.co.uk; spf=none; auth=pass (cram-md5) smtp.auth=pscs Received: from lmail.pscs.co.uk ([192.168.150.1]) by mail.pscs.co.uk ([192.168.150.185] running VPOP3) with ESMTPSA (TLSv1.3 TLS_AES_256_GCM_SHA384); Wed, 12 Oct 2022 21:43:25 +0100 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pscs.co.uk; q=dns/txt; s=lmail; h=From:To:CC:Date:Message-ID:In-Reply-To:References:Subject:MIME-Version :Content-Type:Content-Transfer-Encoding:Reply-to:Sender; t=1665607095; x=1666211895; bh=kWetB37HbkZpJu/Sdmye8yOey8bm8Ypb957oqKGomQs=; b=bwWNRYIKrYMjGqiTeKM0RERW+VDyMGNrbvm7m9w6VkhbI4oGsVQArG9Bai8PHedzT9KpZgvM jDl9xAafNUk+eTEjkBLi8Fd3Z6wdPdbirk4pGKhTS41zDxsQ86UdSFokf9FQIBMHxpamHuCMEu 5DH9DqbLNJicQjrPDAt+U1FtE= Authentication-Results: lmail.pscs.co.uk; spf=none; auth=pass (plain) smtp.auth=paul Received: from [192.168.57.68] ([82.68.48.206] (82-68-48-206.dsl.in-addr.zen.co.uk)) by lmail.pscs.co.uk ([192.168.150.70] running VPOP3) with ESMTPSA (TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384); Wed, 12 Oct 2022 21:38:14 +0100 From: Paul Smith To: Scott Ribe , Ebin Jozer CC: "pgsql-admin" Date: Wed, 12 Oct 2022 21:38:11 +0100 Message-ID: <183cdeb4338.2923.9bfe8bcc586ac955e423c0e3d5444448@pscs.co.uk> In-Reply-To: <9571D051-5B4F-45FB-A52B-9D84C601B7DC@elevated-dev.com> References: <7ce8278e-f943-74d4-ca73-cbf9e422f784@jakobs.com> <9571D051-5B4F-45FB-A52B-9D84C601B7DC@elevated-dev.com> User-Agent: AquaMail/1.39.0 (build: 103900203) Subject: Re: Postgresql community edition upgrade MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="183cdeb451839b6292327737fe" X-Authenticated-Sender: paul X-Server: VPOP3 Enterprise V8.4 - Registered X-Organisation: Paul Smith Computer Services X-VPOP3Tester: 12 345 X-Authenticated-Sender: pscs List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk This is a multi-part message in MIME format. --183cdeb451839b6292327737fe Content-Type: text/plain; format=flowed; charset="us-ascii" Content-Transfer-Encoding: 8bit On 12 October 2022 18:29:12 Scott Ribe 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 --183cdeb451839b6292327737fe Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable


On 12 October 2022 18:29:12 Scott Ribe <scott_ribe@el= evated-dev.com> wrote:
(I think even if you use link mode, it doesn't modify or= iginal 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.)

<= div dir=3D"auto">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 w= ith a minor (documented) step. 

IIRC, the data files (in /data/base) are linked (and unchang= ed by the process). The control files, transaction logs, etc aren't, but t= he old control files are "disabled" to prevent accidental starting of the = old cluster (it's easy to re-enable it) 

<= /div>
See (17) of the Usage notes
=

Paul


=09 =09
--

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

=09 =09
--183cdeb451839b6292327737fe--