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 1tD4J0-00FdoX-Pq for pgsql-admin@arkaria.postgresql.org; Mon, 18 Nov 2024 16:08:50 +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 1tD4Iy-005nnx-Uo for pgsql-admin@arkaria.postgresql.org; Mon, 18 Nov 2024 16:08:49 +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 1tD4Iy-005nne-Gt for pgsql-admin@lists.postgresql.org; Mon, 18 Nov 2024 16:08:49 +0000 Received: from mail-pj1-x1032.google.com ([2607:f8b0:4864:20::1032]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1tD4Ix-002bG2-2X for pgsql-admin@lists.postgresql.org; Mon, 18 Nov 2024 16:08:48 +0000 Received: by mail-pj1-x1032.google.com with SMTP id 98e67ed59e1d1-2ea39638194so1628837a91.2 for ; Mon, 18 Nov 2024 08:08:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1731946123; x=1732550923; darn=lists.postgresql.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=3pRrESdVWouMDqJ7FtAf+R++esJJqQQNQxd8WIP82/0=; b=Y44QXDM7ix58vhDelWUZ9eH18KTakvqBYQbecKL/hFupA56I7sFWXcQGuus1nwKobF WuHRIYyzxJ5ALwukLMeXDDHMuvR4PhCos6I4teE2PDtJU6LOnHOMEvzY7vT0J8gJvnRq WpefPTV+dgU+YdVsGMjy41qBN0z+9R33JZ6BeZYaNdtdun0A78ogzLxJ/uA52J8/1Th8 UQOiPd9aCH9rTNPrP3chdG/eG4QqrBfNP4n5XFy+Luvi6FnXbz2oNUZczbWvehXNz7lU kScr/+85bk/TFDSwTxueh1GWSUbkflzOoWOGeaJfUGr325nSi26kW0noEBu3QxETn/Vd FRYg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1731946123; x=1732550923; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=3pRrESdVWouMDqJ7FtAf+R++esJJqQQNQxd8WIP82/0=; b=KIdxv5EjkH1vcmPKLJh82L8ukoWXR4oL3PhtO3kyUj7eWYiqRpxX19H81afD3K9EJi 7WTKfOSLWYfZTCWxWaG1TIYQeAjL8bZfpDEdAkDSxeWIa26JxLGslAun9wnvwcRSmZ4F kKAluNplWsYD4mAza8wWD0cX+3DqiUd5qw1qHU2m2pIH5xa/HH3R1XYX5PxWdhnuTC6u lMN7EmEXlHJJknzyDeGysieFhGsn9lcaCpzgcg0BkSUtJWhJ9q9dxijZeR4iaTfaI293 u8rq9qn+6KH2G86bP466lwTVi/OmpM8JV+qt42pd/RY9Wi8cGWi8aWoQ1oBevcXqFlOG Qw5g== X-Gm-Message-State: AOJu0Yw5vI1E8ZCVw6ho2aOZVnmLDAdWGMuCo0KI3+g1sH7jJL386SZP 4lOlTaCz/Hko7/jGhss+jPOm7daej43k9CYWhqfk8ayuGRHfZq6xOPc60hYPQvVoP0AZzfTqjcz q7l8oWSXr1ZV2nuWaOEoDGbBdtS7PxA== X-Google-Smtp-Source: AGHT+IGuszKVtHcYu2ZnNszywvyGR8qywmCApYcztXcrkzaQ8aQ/x2ZwofjMfLjtUiyeN+FrsGXdoQuRA4WvFeIvVgU= X-Received: by 2002:a17:90b:3c0c:b0:2ea:4150:3f80 with SMTP id 98e67ed59e1d1-2ea4150444fmr9197547a91.18.1731946123455; Mon, 18 Nov 2024 08:08:43 -0800 (PST) MIME-Version: 1.0 From: Motog Plus Date: Mon, 18 Nov 2024 21:38:31 +0530 Message-ID: Subject: Guidance Needed for PostgreSQL Upgrade from 12 to 15 To: pgsql-admin@lists.postgresql.org Content-Type: multipart/alternative; boundary="0000000000007577df06273221d1" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000007577df06273221d1 Content-Type: text/plain; charset="UTF-8" Dear Team, We are in the process of upgrading our PostgreSQL database from version 12 to version 15. I would greatly appreciate your advice on the following: 1. Would it be recommended to use the --link option with the pg_upgrade command, from disk space point of view? Are there any potential downsides to consider? 2. Do you have any suggestions or best practices for performing an efficient upgrade in a replication setup (streaming replication) for both the primary and standby servers? Thank you in advance for your insights and guidance. Best regards, Raman --0000000000007577df06273221d1 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Dear Team,

<= /div>
We are in the process of upgrading our PostgreSQL da= tabase from version 12 to version 15. I would greatly appreciate your advic= e on the following:

1. W= ould it be recommended to use the --link option with the pg_upgrade command= , from disk space point of view? Are there any potential downsides to consi= der?


2. Do you have any suggestions or best practices for performing a= n efficient upgrade in a replication setup (streaming replication) for both= the primary and standby servers?



Thank you= in advance for your insights and guidance.

Best regards,
Raman


--0000000000007577df06273221d1--