Are libpq and libpqxx equivalent?

[mimosa]

Have a look and see if the files mentioned there exist, if so, by all means delete them.

But first, go to the build directory and do

Code: Select all

sudo make uninstall

which will probably go a long way.

Where did you download the tarball you installed from?

Also try:

Code: Select all

sudo slocate -u
locate -i postgre   # or try other search terms

to get a measure of your success, and possibly unearth more candidates for removal.

[Themis]

Thank you, mimosa.
I ran sudo make uninstall, which apparently worked.
Then here’s what I have.

Code: Select all

/var/log/removed_packages/postgresql-9.5.3-x86_64-1salix-removed-2018-01-04,18:29:14
/var/log/removed_scripts/postgresql-9.5.3-x86_64-1salix-removed-2018-01-04,18:29:14
/var/spool/mail/postgres
/var/slapt-get/salix/system/postgresql-9.5.3-x86_64-1salix.txz
/home/steph/dev/postgresql10
/home/steph/dev/postgresql10/postgresql-10.1.tar
/usr/bin/postgres
/usr/share/gtk-doc/html/redland/redland-storage-module-postgresql.html
/usr/share/nano/postgresql.nanorc
/usr/share/cmake-3.5/Help/module/FindPostgreSQL.rst
/usr/share/cmake-3.5/Modules/FindPostgreSQL.cmake
/usr/share/apps/cmake/modules/FindPostgreSQL.cmake
/usr/lib64/libreoffice5.1/share/registry/postgresql.xcd
/usr/lib64/libreoffice5.1/program/services/postgresql-sdbc.rdb
/usr/lib64/libreoffice5.1/program/libpostgresql-sdbc-impllo.so
/usr/lib64/libreoffice5.1/program/libpostgresql-sdbclo.so
/usr/lib64/libreoffice5.1/program/postgresql-sdbc.ini
/usr/lib64/tdbcpostgres1.0.4
/usr/lib64/tdbcpostgres1.0.4/libtdbcpostgres1.0.4.so
/usr/lib64/tdbcpostgres1.0.4/tdbcpostgres.tcl
/usr/lib64/tdbcpostgres1.0.4/pkgIndex.tcl
/usr/lib64/python3.5/site-packages/passlib/handlers/postgres.py
/usr/lib64/python3.5/site-packages/passlib/handlers/__pycache__/postgres.cpython-35.pyc
/usr/lib64/python3.5/site-packages/sqlalchemy/dialects/postgresql
/usr/lib64/python3.5/site-packages/sqlalchemy/dialects/postgresql/pygresql.py
/usr/lib64/python3.5/site-packages/sqlalchemy/dialects/postgresql/dml.py
/usr/lib64/python3.5/site-packages/sqlalchemy/dialects/postgresql/base.py
/usr/lib64/python3.5/site-packages/sqlalchemy/dialects/postgresql/zxjdbc.py
/usr/lib64/python3.5/site-packages/sqlalchemy/dialects/postgresql/psycopg2cffi.py
/usr/lib64/python3.5/site-packages/sqlalchemy/dialects/postgresql/pg8000.py
/usr/lib64/python3.5/site-packages/sqlalchemy/dialects/postgresql/pypostgresql.py
/usr/lib64/python3.5/site-packages/sqlalchemy/dialects/postgresql/ranges.py
/usr/lib64/python3.5/site-packages/sqlalchemy/dialects/postgresql/json.py
/usr/lib64/python3.5/site-packages/sqlalchemy/dialects/postgresql/hstore.py
/usr/lib64/python3.5/site-packages/sqlalchemy/dialects/postgresql/psycopg2.py
/usr/lib64/python3.5/site-packages/sqlalchemy/dialects/postgresql/ext.py
/usr/lib64/python3.5/site-packages/sqlalchemy/dialects/postgresql/__init__.py
/usr/lib64/python3.5/site-packages/sqlalchemy/dialects/postgresql/array.py
/usr/lib64/python3.5/site-packages/sqlalchemy/dialects/postgresql/__pycache__
/usr/lib64/python3.5/site-packages/sqlalchemy/dialects/postgresql/__pycache__/pygresql.cpython-35.pyc
/usr/lib64/python3.5/site-packages/sqlalchemy/dialects/postgresql/__pycache__/dml.cpython-35.pyc
/usr/lib64/python3.5/site-packages/sqlalchemy/dialects/postgresql/__pycache__/base.cpython-35.pyc
/usr/lib64/python3.5/site-packages/sqlalchemy/dialects/postgresql/__pycache__/zxjdbc.cpython-35.pyc
/usr/lib64/python3.5/site-packages/sqlalchemy/dialects/postgresql/__pycache__/psycopg2cffi.cpython-35.pyc
/usr/lib64/python3.5/site-packages/sqlalchemy/dialects/postgresql/__pycache__/pg8000.cpython-35.pyc
/usr/lib64/python3.5/site-packages/sqlalchemy/dialects/postgresql/__pycache__/pypostgresql.cpython-35.pyc
/usr/lib64/python3.5/site-packages/sqlalchemy/dialects/postgresql/__pycache__/ranges.cpython-35.pyc
/usr/lib64/python3.5/site-packages/sqlalchemy/dialects/postgresql/__pycache__/json.cpython-35.pyc
/usr/lib64/python3.5/site-packages/sqlalchemy/dialects/postgresql/__pycache__/hstore.cpython-35.pyc
/usr/lib64/python3.5/site-packages/sqlalchemy/dialects/postgresql/__pycache__/psycopg2.cpython-35.pyc
/usr/lib64/python3.5/site-packages/sqlalchemy/dialects/postgresql/__pycache__/ext.cpython-35.pyc
/usr/lib64/python3.5/site-packages/sqlalchemy/dialects/postgresql/__pycache__/__init__.cpython-35.pyc
/usr/lib64/python3.5/site-packages/sqlalchemy/dialects/postgresql/__pycache__/array.cpython-35.pyc
/usr/lib64/python3.5/site-packages/alembic/ddl/postgresql.py
/usr/lib64/python3.5/site-packages/alembic/ddl/__pycache__/postgresql.cpython-35.pyc
/etc/rc.d/rc.postgresql
/etc/logrotate.d/postgresql

Regarding this, I guess Pyhton, LibreOffice and co have nothing to do with the PostgreSQL installation I’ve done, am I wrong?

I still have a /usr/local/pgsql/ folder. Should I remove it, too?

Edit: I forgot to answer your question. I downloaded the sources directly from the PostgreSQL official website.

[mimosa]

I'd remove the last two files, the rest should be harmless:

Code: Select all

/etc/rc.d/rc.postgresql
/etc/logrotate.d/postgresql

And also /usr/local/pgsql/

Then build the package by downloading all the files here
http://slackware.uk/salix/x86_64/extra- ... ostgresql/
and putting them together in a directory by themselves.
EDIT This can be done most simply by downloading the slackbuild tarball and unpacking it locally:

Code: Select all

wget https://slackbuilds.org/slackbuilds/14.2/system/postgresql.tar.gz
tar -xf postgresql.tar.gz
cd postgresql

Download the source tarball of the more recent version and put it in the same directory. Edit the version number in the SlackBuild so it corresponds to the new version:

Code: Select all

nano postgresql.SlackBuild
VERSION=${VERSION:-9.6.4}  #change 9.6.4 to (I assume) 10.1

Make the buildscript executable and run it:

Code: Select all

chmod +x postgresql.SlackBuild
sudo ./postgresql.SlackBuild

If all goes well, it will place the new package in /tmp. Install it as follows:

Code: Select all

sudo spkg /tmp/postgresql-9.5.3-x86_64-1_SBo.tgz #the filename may be slightly different, and will have the higher version number.

However, it is possible the build will fail because of differences in the new version. If so, please let us know and maybe a solution can be found!

EDIT You will also need to add the package to the "excludes" in Gslapt/slapt-getrc, otherwise your package will get downgraded to the repo version every time you do an upgrade. If you are not sure how to do this, please ask once you have successfully built and tested the package.

[Themis]

Thanks, mimosa!
You should not have bothered you with all this, I’m a bit embarrassed… I think I’ve put the car before the horse, so I’ll try your solution in a VM as soon as possible and use the version in the repo for my regular Salix installation.

(Also, sorry for the delay. I know that sometimes I’m late to answer. I’m dealing with some health problems this year, so that plus my jobs and studies, I sometimes don’t know where to start anymore. I mentioned this just to let you know it has nothing to do with some kind of laziness. )