MIME-Version: 1.0
From: Motog Plus <mplus7535@gmail.com>
Date: Sat, 10 Aug 2024 13:06:49 +0530
Message-ID: 
 <CAL5GnivDaB509Gu4K9veJT6073jS2yehdpyrwjyKe2x6PSA2Og@mail.gmail.com>
Subject: Seeking Guidance on Upgrading from PostgreSQL 12 to 1
To: pgsql-admin@lists.postgresql.org
Content-Type: multipart/alternative; boundary="00000000000055537c061f4f5399"
Archived-At: 
 <https://www.postgresql.org/message-id/CAL5GnivDaB509Gu4K9veJT6073jS2yehdpyrwjyKe2x6PSA2Og%40mail.gmail.com>
Precedence: bulk

--00000000000055537c061f4f5399
Content-Type: text/plain; charset="UTF-8"

Dear PostgreSQL Admins,

I hope this message finds you well. We are currently running PostgreSQL 12
in dev as well as prod environment . However, with the end of support for
this version scheduled for November 2024, we are considering upgrading to a
higher version, particularly PostgreSQL 16.

I would greatly appreciate your insights on the following points:

1. **Upgrading to PostgreSQL 16**: Would upgrading to version 16 be a
prudent decision, given the advancements and changes since PostgreSQL 12?
Are there any significant concerns or benefits that we should be aware of
before making this decision?

2. **Pre-Upgrade and Post-Upgrade Checks**: Could you please suggest the
critical checks we need to perform prior to the upgrade to ensure it is
successful? Additionally, what post-upgrade checks should be conducted to
confirm everything is functioning as expected?

3. **Upgrade Resources**: Are there any recommended links, videos, or other
resources that can guide us through the upgrade process, especially from
version 12 to 16?

4. **Application Impact**: If we proceed with the upgrade on the same host,
could there be any potential changes or impacts on the application side
that we should be prepared for?

5. **pg_upgrade Functionality**: When using `pg_upgrade`, does it
effectively copy all user-defined functions, extensions, sequences, along
with other database objects like tables, indexes, and schemas? Are there
any specific objects or elements that `pg_upgrade` does not handle, which
we should manually address?

Your advice and guidance will be invaluable as we prepare for this critical
upgrade.

Thank you in advance for your support.

Best regards,
Raman

--00000000000055537c061f4f5399
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto"><div dir=3D"auto">Dear PostgreSQL Admins,</div><div dir=
=3D"auto"><br></div><div dir=3D"auto">I hope this message finds you well. W=
e are currently running PostgreSQL 12 in dev as well as prod environment . =
However, with the end of support for this version scheduled for November 20=
24, we are considering upgrading to a higher version, particularly PostgreS=
QL 16.</div><div dir=3D"auto"><br></div><div dir=3D"auto">I would greatly a=
ppreciate your insights on the following points:</div><div dir=3D"auto"><br=
></div><div dir=3D"auto">1. **Upgrading to PostgreSQL 16**: Would upgrading=
 to version 16 be a prudent decision, given the advancements and changes si=
nce PostgreSQL 12? Are there any significant concerns or benefits that we s=
hould be aware of before making this decision?</div><div dir=3D"auto"><br><=
/div><div dir=3D"auto">2. **Pre-Upgrade and Post-Upgrade Checks**: Could yo=
u please suggest the critical checks we need to perform prior to the upgrad=
e to ensure it is successful? Additionally, what post-upgrade checks should=
 be conducted to confirm everything is functioning as expected?</div><div d=
ir=3D"auto"><br></div><div dir=3D"auto">3. **Upgrade Resources**: Are there=
 any recommended links, videos, or other resources that can guide us throug=
h the upgrade process, especially from version 12 to 16?</div><div dir=3D"a=
uto"><br></div><div dir=3D"auto">4. **Application Impact**: If we proceed w=
ith the upgrade on the same host, could there be any potential changes or i=
mpacts on the application side that we should be prepared for?</div><div di=
r=3D"auto"><br></div><div dir=3D"auto">5. **pg_upgrade Functionality**: Whe=
n using `pg_upgrade`, does it effectively copy all user-defined functions, =
extensions, sequences, along with other database objects like tables, index=
es, and schemas? Are there any specific objects or elements that `pg_upgrad=
e` does not handle, which we should manually address?</div><div dir=3D"auto=
"><br></div><div dir=3D"auto">Your advice and guidance will be invaluable a=
s we prepare for this critical upgrade.</div><div dir=3D"auto"><br></div><d=
iv dir=3D"auto">Thank you in advance for your support.</div><div dir=3D"aut=
o"><br></div><div dir=3D"auto">Best regards,=C2=A0=C2=A0</div><div dir=3D"a=
uto">Raman</div></div>

--00000000000055537c061f4f5399--