Re: Help in vetting error using "pg_upgrade" - steps for Postgres DB upgrade from Ver 13.X to ver 14.X/15.X and issue with python binaries

On 1/28/25 08:23, Bharani SV-forum wrote:
> Team
> Need your help.
> We are trying to use existing VM with underlying OS = Amazon Linux 2 
> (AL2)  along with Pgsql ver 13.X community edn.
> Trying to upgrade from 13.X to 15.X and had hit the bottleneck for the 
> mandate to have python ver 3.X binaries.
> We have limitation with the existing VM with AWS and currently AL2 uses 
> the |yum| package manager that has a hard dependency on Python 2.7 and 
> the pgsql ver 15. needed Ver 3.x python binaries and the package 
> community edition (pgsql ver 15.x) "postgresql15-contrib.." is not 
> getting installed.
> 
> We have limitation , where the application being used is having python 
> ver 2.x binaries and we cannot install python 3.x binaries , as  we have 
> the underlying OS with AL2 which is having "a hard dependency on Python 2.7"
> 
> In lieu of using pgsql ver 15.X. We are OK to upgrade to the next 
> version which is 14.X  from existing ver 13.X.
> 
> Can anyone re-confirm if the Community edition (pgsql ver14.x)  - 
> "postgresql14-contrib .." needed python ver 2.X binaries or Ver 3.X 
> binaries.

 From here:

https://yum.postgresql.org/14/redhat/rhel-7-x86_64/repoview/postgresql14-contrib.html

postgresql14-contrib-14.15-1PGDG.rhel7.x86_64

hstore_plpython3.so
jsonb_plpython3.so
ltree_plpython3.so

So I'm going to say yes Python 3 is needed.

FYI I don't see those files in postgresql13-contrib.

If you want to move forward you need to either install Python 3 in your 
current distro or use a different distro.

> 
> I cross checked and found one of the url " Install Postgres v14 + 
> -contrib on AWS Linux 2 | the gabriellephant 
> <https://gorthx.wordpress.com/2022/02/08/install-postgres-v14-contrib-on-aws-linux-2/>" is quoting pgsql ver 14.x
neededpython ver 3.x binary
 
> 
> On Friday, January 24, 2025 at 02:14:56 PM EST, Adrian Klaver 
> <adrian.klaver@aklaver.com> wrote:
> 
> 
> 
> 

-- 
Adrian Klaver
adrian.klaver@aklaver.com