Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtps  (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.94.2)
	(envelope-from <pgsql-general-owner+archive@lists.postgresql.org>)
	id 1uAcNV-00HTFN-L6
	for pgsql-general@arkaria.postgresql.org; Thu, 01 May 2025 22:27:38 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.94.2)
	(envelope-from <pgsql-general-owner+archive@lists.postgresql.org>)
	id 1uAcNT-005hnh-Kc
	for pgsql-general@arkaria.postgresql.org; Thu, 01 May 2025 22:27:36 +0000
Received: from makus.postgresql.org ([2001:4800:3e1:1::229])
	by malur.postgresql.org with esmtps  (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.94.2)
	(envelope-from <justin@postgresql.org>)
	id 1uAcNT-005hnY-9x
	for pgsql-general@lists.postgresql.org; Thu, 01 May 2025 22:27:36 +0000
Received: from meldrar.postgresql.org ([2a02:c0:301:0:ffff::31])
	by makus.postgresql.org with esmtps  (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.96)
	(envelope-from <justin@postgresql.org>)
	id 1uAcNS-000alM-1t
	for pgsql-general@postgresql.org;
	Thu, 01 May 2025 22:27:35 +0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed;
	d=postgresql.org; s=20171124; h=Content-Transfer-Encoding:Content-Type:
	Message-ID:References:In-Reply-To:Subject:Cc:To:From:Date:MIME-Version:Sender
	:Reply-To:Content-ID:Content-Description;
	bh=gHkD748kSJKTPL45b0murD9swujcsMQuD+bXtPiFowM=; b=j97p9Ep137bQIF7O99Nxpzd0Re
	bZpLI/GC4VwDVDg0t8uWuJQOXAkf4BweHJSm6V/HPv5QQHsZX/jZKySKO9wXIwUtFgwcqCS1R7iKW
	AQB9ceZlsbFD0XV5d5wKRx89DtSj5otl8pEkjezrv4EhhHuKkyRuYdtNdNeOckacb5xCYY3I9BRW3
	n56kWOThqK9CMOevI2UZ97Ge7iD6GenfxEMK+bpl1ZYUsCAZkzRVVBFBEI3OGSd1TiWeBfQsqOgTy
	g9J3rXTS9Vowbrx5o1oGIwRJSz3BS889ChVeYq0KU+pyif6SGHRrbZEqWJbrsh0Gah+vTOJWAhUf8
	QdhQDEIg==;
Received: from meldrar.postgresql.org ([87.238.57.231] helo=webmail.postgresql.org)
	by meldrar.postgresql.org with esmtpsa  (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.96)
	(envelope-from <justin@postgresql.org>)
	id 1uAcNQ-001L3C-1P;
	Thu, 01 May 2025 22:27:33 +0000
MIME-Version: 1.0
Date: Fri, 02 May 2025 08:27:30 +1000
From: Justin Clift <justin@postgresql.org>
To: Durumdara <durumdara@gmail.com>
Cc: Postgres General <pgsql-general@postgresql.org>
Subject: Re: Upgrading PG11 to PG17 without dump/restore
In-Reply-To: <CAEcMXh=PtUgwj5exvV8PpyvY0H=eOtUkn-wAPcn7p35vkeHzmg@mail.gmail.com>
References: <CAEcMXh=PtUgwj5exvV8PpyvY0H=eOtUkn-wAPcn7p35vkeHzmg@mail.gmail.com>
Message-ID: <f49758e620f7dfa42207d4c7ffdaffa0@postgresql.org>
X-Sender: justin@postgresql.org
Content-Type: text/plain; charset=US-ASCII;
 format=flowed
Content-Transfer-Encoding: 7bit
List-Id: <pgsql-general.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-general@lists.postgresql.org>
List-Owner: <mailto:pgsql-general-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-general>
Archived-At: <https://www.postgresql.org/message-id/f49758e620f7dfa42207d4c7ffdaffa0%40postgresql.org>
Precedence: bulk

On 2025-05-01 23:06, Durumdara wrote:
<snip>
> The PG_Upgrade is not possible because of lesser space and too old 
> debian.

As a data point, pg_upgrade has an option to do an in-place upgrade 
which
reuses the vast majority of the data files as they are on disk, rather 
than
making a copy.

It's useful for larger databases, and for situations where you don't 
have
much space.

BUT, you *do* have backups don't you?

Because stuff *can* go wrong, even though it's not common. ;)

Regards and best wishes,

Justin Clift