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 1tIqhK-00H2yn-3a for pgsql-general@arkaria.postgresql.org; Wed, 04 Dec 2024 14:49: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 1tIqhH-000PWE-Kn for pgsql-general@arkaria.postgresql.org; Wed, 04 Dec 2024 14:49:48 +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 1tIqhH-000PVr-89 for pgsql-general@lists.postgresql.org; Wed, 04 Dec 2024 14:49:48 +0000 Received: from mail-ot1-x329.google.com ([2607:f8b0:4864:20::329]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1tIqhF-0011mH-Hk for pgsql-general@postgresql.org; Wed, 04 Dec 2024 14:49:47 +0000 Received: by mail-ot1-x329.google.com with SMTP id 46e09a7af769-71d3e506981so2904497a34.1 for ; Wed, 04 Dec 2024 06:49:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1733323784; x=1733928584; darn=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=G2gr4iTMEK9luXRFMXFG1BWOkIyR0OsBMYiI1/F1sDs=; b=LZBM2xF9VCshORVpdHZc7agJsmuctBkd+SZmYQdfMgRkj6mhSrdUmwq6hV7zmtWip5 P8gIfXdj82d1h+aSKxB2otfSCz226h5uH+kAWpVSixBceiLoDkiRZ0shHde1PcT92h92 W5Z0X/f5iX6XPJUCZXcr7K0UT/2FjB3MzZdZ7tk6lUV5RZyLYCijL5+vxReANZBuggX/ asUW/kbiT2dps/5bgo+vgcqDTETDcwaH6HvQnEkrNjnDsp71FC3J9UJYqjutsEexsWg3 kwwhDvf5blrVKNIQN+uv5kAtXKy20X6Bsv5P3Ig+x+NgCw0GPjTOmkJ/N3B6azpA+sIp ihFA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1733323784; x=1733928584; 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=G2gr4iTMEK9luXRFMXFG1BWOkIyR0OsBMYiI1/F1sDs=; b=DZleb/xVu9HzuHFz3SSzbmf9dmIaXr2KUv8x+FHYXBtxF3/ifH33cCSXp+ZHA6N82K RJdUZsyVHPxkVTf3xVY/i8dOIUZWPrnuZZT2iMFv4l0zveSx4nJ1/aQ3AQvqNXrNWHhr fSaaQrpoSvXlp5lJR0hnyH75cQrqCbRD82nCjQHu98kaK0teZGAZ1lr/HYREQGhd2v73 NtSaO04W74s7jtsukfusCFutD9vmb8BzTB1is1H94igxhNs782t5gW2EbTPw60EyC2eL 02v+S1Xs0FdSjj8BJNN0xr0UAZgO2u9wVcCKIUt2fj63VxdP/ml0HTwKyqBe29HuQ1Re q7tg== X-Gm-Message-State: AOJu0YzFrYHqY/o4xfF0kRyQ9OfkoR4tRrXzvBYiksfgr5iM8k7elgd0 S7Ew92Aux8AbXEWb+k+XOyRz1LO4H08XH9ADT7HBBgrzfAaei4ooqj9e0SAHiaDcFlmxXXa9IkW yCUcISkdsT2kESSnbdxFRycIy94yklH3K X-Gm-Gg: ASbGncv+7u80vJAdU+pgtcfXCxeCK55yLooTxo5VLEM/BtQmFSQnD5k0ioF5QonVRHN 42vsb1EdOXjHLj9b52lw43QP+Cig8HPxAdfTvhE5cTCGKpqsdmEE2AKQHgQqr5QRBxQ== X-Google-Smtp-Source: AGHT+IGBYip1E9ApLDi5QFcs24b6YCb4SnmVhzH3KF5+/nTh/ZU5gYUy+B++XOy5kQDGGnsr/Ef8J1cwyBKVudFlSSA= X-Received: by 2002:a05:6830:dc7:b0:71d:5f65:ce2f with SMTP id 46e09a7af769-71dad6d43femr7473635a34.22.1733323784137; Wed, 04 Dec 2024 06:49:44 -0800 (PST) MIME-Version: 1.0 References: <0558ddd4d71641bdb41fa49b2425f73c@safrangroup.com> <98965993.3138805.1731699978332@mail.yahoo.com> <564950518.5117550.1733177884387@mail.yahoo.com> <07ab2d83-ffe5-4bec-9626-22a68f732579@aklaver.com> <273a88dc-4134-47d5-bc19-30ff5f97926c@aklaver.com> <498dfb34-4dd7-4f48-8188-355e1488d7e6@aklaver.com> <1061066336.5835157.1733316137292@mail.yahoo.com> In-Reply-To: <1061066336.5835157.1733316137292@mail.yahoo.com> From: Ron Johnson Date: Wed, 4 Dec 2024 09:49:33 -0500 Message-ID: Subject: Re: Help in vetting my steps for Postgres DB upgrade from Ver 13.X to ver 15.X To: pgsql-general Content-Type: multipart/alternative; boundary="0000000000006f3551062872e495" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000006f3551062872e495 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Wed, Dec 4, 2024 at 7:42=E2=80=AFAM Bharani SV-forum wrote: > Team /Ron/Adrian > > Wann to reconfirm > we have an setup with > > new server will be with > > will be following the following suggestion > > *On old VM* [ existing server with OS "Amazon Linux release 2 (Karoo) " > present in aws "us-east-1 region" and along with postgresql ver 13.16.2 = - > community edn ] > > - "take offline full backup (PG_DATA folder alone) using OS command" > > *On new VM [OS "Amazon Linux 2023 " in aws region=3Dus-east-1 and intende= d > db as "postgresql 15.10 - community edn" ] * > > - "Restore offline full backup (PG_DATA folder alone) using OS command" > - create postgres unix userid > - install postgresql ver 15.10 binaries > - setup respective env variable to point correctly for PG_DATA > - will follow "pg_upgrade" > > > my question is > a) is the above said steps is correct with the given existing and propose= d > setup > No. You're vastly overcomplicating things. > b) is their any known issues using "cross over using pg_upgrade " option > between the server's having below said operating system > There is no "cross over using pg_upgrade" because it does not exist. When migrating from OldServer to NewServer, your options are: A) pg_dump/pg_restore B) Logical Replication > *- source =3D existing server with OS =3D *Amazon Linux release 2 (Karoo)= " > present in aws "us-east-1 region" and along with postgresql ver 13.16.2 = - > community edn > vs > target - different server *OS "Amazon Linux 2023 " in aws > region=3Dus-east-1 and intended db as "postgresql 15.10 - community edn"* > --=20 Death to , and butter sauce. Don't boil me, I'm still alive. lobster! --0000000000006f3551062872e495 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Wed, Dec 4, 2024 at 7:42=E2=80=AFAM Bh= arani SV-forum <esteembsv-f= orum@yahoo.com> wrote:
Team /Ron/Adrian

<= div dir=3D"ltr">Wann to reconfirm
we have= an setup with=C2=A0

n= ew server will be with=C2=A0

will be following the following suggestion
<= br>
existing server with OS=C2=A0"Amazon Lin= ux release 2 (Karoo) " present in aws "us-east-1 region" and= along with postgresql ver 13.16.2=C2=A0 - community edn ]

=C2=A0- "take offline full backup = (PG_DATA folder alone)=C2=A0 using OS command"

On new VM [OS "Amazon Linux 2023 " in aws reg= ion=3Dus-east-1 and intended db as "postgresql 15.10 - community edn&q= uot; ]=C2=A0

=C2=A0- "Restore offline full backup (PG_DATA folder a= lone) using OS command"
= - create postgres unix userid
- install postgresql ve= r 15.10 binaries
- setup respective env variable to p= oint correctly for PG_DATA
- = will follow "pg_upgrade"=


my question is=C2=A0
a) is the above said steps is correct with the giv= en existing and proposed setup

No.=C2=A0 You're vastly overcomplicating thing= s.
=C2=A0
=
b) is their any known issues using "cross ov= er using pg_upgrade " option between the server's having below sai= d operating system=C2=A0
<= div>
There is no=C2=A0"cross over using pg_upgrade"= because it does not exist.

When migrating from Ol= dServer to NewServer, your options are:
A) pg_dump/pg_restore
B) Logical Replication
=C2=A0
- source =3D exist= ing server with OS =3D=C2=A0Amazon Linux release 2 (Karoo) " prese= nt in aws "us-east-1 region" and along with postgresql ver 13.16.= 2=C2=A0 - community edn=C2=A0
vs
target - different server=C2=A0OS "Amazon Linux 2023 " in aws region=3Dus-eas= t-1 and intended db as "postgresql 15.10 - community edn"<= /b>
<= div>
=C2=A0
--
= Death to <Redacted>, and butter sauce.
Don't boil me, I'm= still alive.
<Redacted> lobster!
--0000000000006f3551062872e495--