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 1tD5Ie-00FmFE-Cq for pgsql-admin@arkaria.postgresql.org; Mon, 18 Nov 2024 17:12:32 +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 1tD5Hc-0064U2-V2 for pgsql-admin@arkaria.postgresql.org; Mon, 18 Nov 2024 17:11:29 +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 ) id 1tD5Hc-0064Tu-Hm for pgsql-admin@lists.postgresql.org; Mon, 18 Nov 2024 17:11:29 +0000 Received: from mail-ot1-x333.google.com ([2607:f8b0:4864:20::333]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1tD5Ha-002YWB-Bh for pgsql-admin@lists.postgresql.org; Mon, 18 Nov 2024 17:11:27 +0000 Received: by mail-ot1-x333.google.com with SMTP id 46e09a7af769-71808b6246bso1129525a34.2 for ; Mon, 18 Nov 2024 09:11:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1731949885; x=1732554685; darn=lists.postgresql.org; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=iZpYXFCS1RC+Boof2C9H7fITqWjlk9or2fcuINmZLLk=; b=JPNiUnYIkD9srwbvPxHGCMI/+3MmZxccBrQOSTdOvXFPDjtB/rhUE7lVsmpkL/Vy1M SEp+HT6kVNPgx21cN4mk0h4NYeL+G4mBAwWdIkAI6RjMWnTD61tFxSc3wkmQCWJhmRC9 px4zUIxwEbX7ECDwvB89Y89ZvPQ7hn9Es/2+H6LQumlHQwdTNM7Uu+u8zu851JTzH2JO MGIKBHOyucZiFuCqERLTNLlM9GQWWm2FHJGsSjjWTH2xJ9mToZGLvdAhf74FIdf8RTc/ etEVNEznsimVx5zgJORW0MK6RTkYM0+DoD5qaO+gJGJyN5ke9DlT+8s9X+SaZwvENznk OFHg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1731949885; x=1732554685; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=iZpYXFCS1RC+Boof2C9H7fITqWjlk9or2fcuINmZLLk=; b=NHiVCu1WCwDwEdsQwLqUZiPkH60uxh/11JgNmlRyyrzX+vZ6kne5WjSDGYb2vxkHlp sv2x05IaSQB71Gp/WeASJpmcy03K0JAVCCPfIkL8tbLkRRUAbDfVsDlHE/YqCzW4niBb TYIVWiPXPiZD/gcbVwmg3w/noFlAPb+oD88fNZtE+yTSsiKD3nAFgcpuLsp8FXUT+H8l 5vUXf93rzLCxNUkO2YUqGBMZ8o8ttjwci3XSrJgQyr+bfFL8NYN/4CQE0LeBTGEWfhh/ FMhqIzK26Tn077OU+avGieqs90lW0PLmlZfeoN2aviUCtwLwLJqDlNjUYbUiAJxJJJ1m aw+Q== X-Gm-Message-State: AOJu0YwhnS9Bgn4YDvyI9QFM5x7gf+fWbETtHHiS3eNr0+C4aZVZOKPL mHpGLJpEI83zNBrkRLPVcnpRWgCO7Qr8t5srveZl4Ku5WqI9jJukAWbCR+sOBJrRWLNQgXegN0Y 5NdCrA2S6Sl7wwhSss3uGFExOVpIjGA== X-Google-Smtp-Source: AGHT+IFbzhjQkBG+miC8ZRhlNVlH+MkHaatgLzixNw7BlfK+3hITujNWqkK8EE6AtElJIbZcMqjPP9snQa/Vl4mSGZc= X-Received: by 2002:a05:6830:6110:b0:717:fdbb:146d with SMTP id 46e09a7af769-71a778fef1fmr12905902a34.2.1731949885322; Mon, 18 Nov 2024 09:11:25 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Ron Johnson Date: Mon, 18 Nov 2024 12:11:14 -0500 Message-ID: Subject: Re: Guidance Needed for PostgreSQL Upgrade from 12 to 15 To: Pgsql-admin Content-Type: multipart/alternative; boundary="000000000000aefc9206273301ae" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000aefc9206273301ae Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Mon, Nov 18, 2024 at 11:08=E2=80=AFAM Motog Plus w= rote: > Dear Team, > > We are in the process of upgrading our PostgreSQL database from version 1= 2 > 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? > Yes. > Are there any potential downsides to consider? > Very much: it's a one-way journey. No rolling back if something goes wrong= ! > 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? > Streaming replication is not an upgrade method. Logical replication is absolutely a valid method of upgrading PG on one server to PG on a different server. --=20 Death to , and butter sauce. Don't boil me, I'm still alive. lobster! --000000000000aefc9206273301ae Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Mon, Nov 18, 2024 at 11:08=E2=80=AFAM = Motog Plus <mplus7535@gmail.com> wrote: