Re: postgresql14-contrib does not install with libpython 3.7

Hi, Alex
This is what I did using Daniel suggestions:
[root]# yum groupinstall "Development tools"

[root]# useradd postgres

[root]# yum install readline-devel
[root]# yum install zlib-devel

[postgres]$ wget https://ftp.postgresql.org/pub/source/v14.2/postgresql-14
.2.tar.bz2

[postgres]$ tar -xvf postgresql-14.2.tar.bz2

[root]# mkdir /usr/pgcontrib_py/pgsql-14

[root]# cd postgresql-14.2/

[root]# PYTHON=/bin/python3

[root]# ./configure --prefix=/usr/pgcontrib_py/pgsql-14 --with-python

[root]# cd contrib

[root]# gmake clean

[root]# gmake

[root]# gmake install

After this, the content at */usr/pgcontrib_py/pgsql-14* could be compressed
and could be uncompressed under a PG 14 installation at /usr/pgsql-14/

Best regards
Marcia

On Thu, Oct 19, 2023 at 7:35 PM Alex Williams <valenceshell(at)protonmail(dot)com>
wrote:

> Hi Tom/Maria,
>
> I'm in a similar situation using a Amazon Linux 2 server instance and by
> default it comes with Python 3.7. I uninstalled Python 3.7 and installed
> Python 3.6 and the postgres contrib-14 package installed without issue.
>
> Of course, there was a recent security patch where we now need to remove
> Python 3.6 and use Python 3.7 to apply the vulnerability update.
>
> Trying it again, with Python 3.7, I get:
> Error: Package: postgresql14-contrib-14.9-2PGDG.rhel7.x86_64 (pgdg14)
> Requires: libpython3.6m.so.1.0()(64bit)
> Available: python3-libs-3.6.2-3.amzn2.0.2.x86_64
> (amzn2extra-python3)
>
> Can you please let me know what you did to get it work with Python 3.7. I
> assumed there was a source postgres-contrib14 location I could wget and
> build against Python 3.7 but I can't find it, so I assume someone is
> manually adding various extensions to this and creating packages, but
> offering no source to build with?
>
> Thanks in advance for your help,
>
> Alex
>
>
>
> > Yeah ... I don't have a RHEL7 installation handy, but the official Python
> > installation in my RHEL8 workstation is 3.6.8, so it's impossible to
> > believe that RHEL7 shipped with Python 3.7. What you have there is a
> > nonstandard software environment, and if you want to stick with it that's
> > going to mean doing some of your own building.
> >
> > However, rather than compiling directly from source as Daniel suggests,
> > I'd suggest grabbing the SRPM for the package version you want and
> > building RPMs from that locally. This is, generally, even easier than
> > building raw source, and it will make for a much easier transition from
> > your existing RPM-based installation of PG.
> >
> > regards, tom lane
>