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 ) id 1rid5M-000g5W-8p for pgsql-general@arkaria.postgresql.org; Fri, 08 Mar 2024 16:28:40 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1rid5K-00E8ol-Kn for pgsql-general@arkaria.postgresql.org; Fri, 08 Mar 2024 16:28:39 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rid5K-00E8od-9Z for pgsql-general@lists.postgresql.org; Fri, 08 Mar 2024 16:28:38 +0000 Received: from mail-yw1-x1136.google.com ([2607:f8b0:4864:20::1136]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1rid5D-003Sq5-Br for pgsql-general@lists.postgresql.org; Fri, 08 Mar 2024 16:28:37 +0000 Received: by mail-yw1-x1136.google.com with SMTP id 00721157ae682-609fc742044so17214207b3.1 for ; Fri, 08 Mar 2024 08:28:31 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1709915310; x=1710520110; h=content-transfer-encoding:in-reply-to:from:references:to :content-language:subject:user-agent:mime-version:date:message-id :dkim-signature:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=QoFcbktw+J1qnebjKm8ahisdA5hhkA0fTMWAb0bm9Wo=; b=dhGzytM5+GjmkayofdVktFIsH1KkSPBSAAf52XKc5qX3foCnkhEGY2kONNmajQjVoK hXgzByo2jwAZZyTsIUlpzWjTWJl+ey+3hg7y3NXinwp93y622mxJ9zEivzwCHTw9JUga mCqRDwFBRkaWY69N5y43bDnTivaqVdSBfhmQHUSDouygnPkYD5GAPse20OSJrnrZcqz4 DtdTJuY/e3muQSv4i/AFyxh+q0pTCZWANyrf1O8lX+D239coQ7aLyty7q2ZSSutwyRes mxb85Gk6LCvTUu4bd0zWqzE2YKzXs5/wZsNdNWtAalFNBx/hKfIhSOV0tvex5yY34WjL voKA== X-Forwarded-Encrypted: i=1; AJvYcCX9E6HBPOyJseW+7eglsxlbM//9gDSDPXqKNTn5VqLmswwgf3/S6V7y31+amCAYepy6AUnudkKSU2Ud263hEzV1ToyQM0TnBaG60RrkpuuBDgFV X-Gm-Message-State: AOJu0YxFGaBPG3Vs9FOXXQlLK+fCIHLLNUTeoEYmv1pRk9e9+Oc38noj ILs5BRLhi1xJDYlUYRZqDkICaLYrj1E9UwhX7CGoiprRbs7ToD0o4XnPB/WqXQgM56N2nTGR X-Google-Smtp-Source: AGHT+IGYDwaWkOjgF1FzMBoSPvlZYWHCAafb107XlJb9C840z7VAkEz7IxnDSAZiDF9BTHHCYYJq3g== X-Received: by 2002:a81:6c92:0:b0:609:efe6:a4ed with SMTP id h140-20020a816c92000000b00609efe6a4edmr6100388ywc.13.1709915309504; Fri, 08 Mar 2024 08:28:29 -0800 (PST) Received: from email.catprosystems.com ([68.79.78.72]) by smtp.gmail.com with ESMTPSA id o15-20020a81ef0f000000b006096ac6112bsm4685313ywm.138.2024.03.08.08.28.28 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 08 Mar 2024 08:28:28 -0800 (PST) Received: from email.catprosystems.com (localhost [127.0.0.1]) by email.catprosystems.com (Postfix) with ESMTP id 4Trs6h2NFvzyj5 for ; Fri, 8 Mar 2024 11:28:28 -0500 (EST) Authentication-Results: email.catprosystems.com (amavis); dkim=pass reason="pass (just generated, assumed good)" header.d=catprosystems.com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d= catprosystems.com; h=content-transfer-encoding:content-type :in-reply-to:from:references:to:content-language:subject :user-agent:mime-version:date:message-id; s=dkim; t=1709915300; x=1712507301; bh=QoFcbktw+J1qnebjKm8ahisdA5hhkA0fTMWAb0bm9Wo=; b= g2uNd9V6xaGzBDoK53SZf5Ch8TAludOzjWuzqAPdO1BeyyyyrTE+51uclHLR9O3H 8dUiGbZuW1gEvXEx0IyS40LxihwPhmnl6vNlMn6OYp+hwptdcqAeyDQPazIWdXLk HMS3Dnp++OQ337xJ/i8yRT2SbMW3EC/0WowtgFlc8tJ+ahTVBjoops8BcpMgeKfu PXg84Ti9OjfuOzebtggutZqYaADnm9phG3GYO0bhVd4kD4qmH6dqzCNoVwdYgwDP 9+UoOetwkU2yPPwSwQTLzit8yEZznBV0Xy2Htuf9IGCOr71fQY9qVy4PIXs9a5H4 tnPFWqcyXA49xtz7FNxk5A== X-Virus-Scanned: amavis at email.catprosystems.com Received: from email.catprosystems.com ([127.0.0.1]) by email.catprosystems.com (email.catprosystems.com [127.0.0.1]) (amavis, port 10026) with ESMTP id JUZunHWH8GSk for ; Fri, 8 Mar 2024 11:28:20 -0500 (EST) Received: from [192.168.101.56] (unknown [192.168.101.56]) by email.catprosystems.com (Postfix) with ESMTPSA id 4Trs6X5qXKzygc; Fri, 8 Mar 2024 11:28:20 -0500 (EST) Message-ID: <88132f81-7e82-4d53-a55a-eede564351da@catprosystems.com> Date: Fri, 8 Mar 2024 11:28:20 -0500 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: v11.5- v15.3 upgrade (linux) Content-Language: en-US To: David Gauthier , pgsql-general@lists.postgresql.org References: From: Yogesh Sharma In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Greetings, On 3/6/24 19:19, David Gauthier wrote: > Hi: > I'm a PG user in a big corp with an IT dept that administers a PG=20 > server/instance that I use.=C2=A0 It's an old install, v11.5, and we ne= ed=20 > to upgrade to v15.3.=C2=A0 They want to bring the upgraded=C2=A0DB up o= n a new=20 > linux vm which has OS upgrades of its own.=C2=A0 So it's a move AND an=20 > upgrade. There are 2 concerns.... > > First has to do with a jump from 11.5 - 15.3 ?=C2=A0 Is it safe to do t= his=20 > given so many major intermediate versions being skipped ? Generally speaking, it is safe from database point of view but you have=20 to verify that application is working as expected with PostgreSQL 15,=20 driver update, any query performance issues, any deprecate features in=20 use, collation differences, and performance verification, etc. PostgreSQL supports dump/restore (slow and longer downtime), binary=20 upgrade using pg_upgrade (faster and low downtime), and logical=20 replication (complex and least downtime). Since OS upgrade is also part=20 of the equation, dump/restore or logical=C2=A0 are better candidates. Due= to=20 OS collation difference I would avoid binary upgrade path. --=20 Kind Regards, Yogesh Sharma PostgreSQL, Linux, and Networking Expert Open Source Enthusiast and Advocate PostgreSQL Contributors Team @ RDS Open Source Databases Amazon Web Services: https://aws.amazon.com