Thread: [GENERAL] Installing module for 9.6, not 9.2, on Centos?
Hi. I recently installed 9.6 on my Centos 6.9 server, alongside a still-running 9.2.
I need to install a module for 9.6 (table_log) that is installed on 9.2.
I took the table_log Makefile and changed it to point to /usr/pgsql-9.6/bin/pg_config instead of 9.2. It is still installing into the 9.2 directory though.
What's the cleanest or most proper way to target 9.6 in this situation? Transcript below, and TIA.
Ken
MODULES = table_log
DATA_built = table_log.sql
DOCS = README.table_log
ifdef USE_PGXS
PGXS := $(shell /usr/pgsql-9.6/bin/pg_config --pgxs)
include $(PGXS)
else
subdir = contrib/table_log
top_builddir = ../..
include $(top_builddir)/src/Makefile.global
include $(top_srcdir)/contrib/contrib-global.mk
endif
[root@hosting table_log-0.4.4]# make USE_PGXS=1 clean
rm -f table_log.so table_log.o
rm -f table_log.sql
[root@hosting table_log-0.4.4]# make USE_PGXS=1
sed 's,MODULE_PATHNAME,$libdir/table_log,g' table_log.sql.in >table_log.sql
gcc -Wall -Wmissing-prototypes -Wpointer-arith -Wdeclaration-after-statement -Wendif-labels -Wmissing-format-attribute -Wformat-security -fno-strict-aliasing -fwrapv -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic -DLINUX_OOM_SCORE_ADJ=0 -fpic -I. -I./ -I/usr/pgsql-9.2/include/server -I/usr/pgsql-9.2/include/internal -D_GNU_SOURCE -I/usr/include/libxml2 -I/usr/include -c -o table_log.o table_log.c
gcc -Wall -Wmissing-prototypes -Wpointer-arith -Wdeclaration-after-statement -Wendif-labels -Wmissing-format-attribute -Wformat-security -fno-strict-aliasing -fwrapv -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic -DLINUX_OOM_SCORE_ADJ=0 -fpic -L/usr/pgsql-9.2/lib -Wl,--as-needed -L/usr/lib64 -Wl,--as-needed -Wl,-rpath,'/usr/pgsql-9.2/lib',--enable-new-dtags -shared -o table_log.so table_log.o
[root@hosting table_log-0.4.4]# make USE_PGXS=1 install
/bin/mkdir -p '/usr/pgsql-9.2/share/contrib'
/bin/mkdir -p '/usr/pgsql-9.2/lib'
/bin/mkdir -p '/usr/pgsql-9.2/doc/contrib'
/usr/bin/install -c -m 644 table_log.sql '/usr/pgsql-9.2/share/contrib/'
/usr/bin/install -c -m 755 table_log.so '/usr/pgsql-9.2/lib/'
/usr/bin/install -c -m 644 .//README.table_log '/usr/pgsql-9.2/doc/contrib/'--
/bin/mkdir -p '/usr/pgsql-9.2/lib'
/bin/mkdir -p '/usr/pgsql-9.2/doc/contrib'
/usr/bin/install -c -m 644 table_log.sql '/usr/pgsql-9.2/share/contrib/'
/usr/bin/install -c -m 755 table_log.so '/usr/pgsql-9.2/lib/'
/usr/bin/install -c -m 644 .//README.table_log '/usr/pgsql-9.2/doc/contrib/'--
AGENCY Software
A Free Software data system
By and for non-profits
(253) 245-3801
learn more about AGENCY or
follow the discussion.
Thanks Adrian, though still no luck for me. The compiling was working OK already, the install still goes to 9.2.
Any further help appreciated! Thanks.
Where did you get the table_log extension
I no longer remember (it's been a few years), but my tgz file was the same as what's on pgfoundry
I usually do something like(using existing Makefile):
PATH=/usr/local/pgsql96/bin/:$PATH make USE_PGXS=1 clean all
...
Though in both cases the extension did not actually compile due to errors.
That worked fine for me. (Somewhere along the way I added these two lines to table_log.c:
+#include <utils/rel.h> |
+#include <utils/timestamp.h>
)
But the install still goes to 9.2:
PATH=/usr/local/pgsql96/bin/:$PATH make USE_PGXS=1 install |
/bin/mkdir -p '/usr/pgsql-9.2/share/contrib'
/bin/mkdir -p '/usr/pgsql-9.2/lib'
/bin/mkdir -p '/usr/pgsql-9.2/doc/contrib'
/usr/bin/install -c -m 644 table_log.sql '/usr/pgsql-9.2/share/contrib/'
/usr/bin/install -c -m 755 table_log.so '/usr/pgsql-9.2/lib/'
/usr/bin/install -c -m 644 .//README.table_log '/usr/pgsql-9.2/doc/contrib/'
Ken
--
AGENCY Software
A Free Software data system
By and for non-profits
(253) 245-3801
learn more about AGENCY or
follow the discussion.
But the install still goes to 9.2:
PATH=/usr/local/pgsql96/bin/:$PATH make USE_PGXS=1 install
Did you do:
PATH=/usr/local/pgsql96/bin/:$PATH make USE_PGXS=1 clean all
I did.
Or is there some environment variable set that could be interfering?
I didn't see anything that would apply. I've attached a dump of environment variables and also a re-run of the compile/install process.
Cheers,
Ken
AGENCY Software
A Free Software data system
By and for non-profits
(253) 245-3801
learn more about AGENCY or
follow the discussion.
Attachment
On Tue, May 23, 2017 at 5:34 PM, Adrian Klaver <adrian.klaver@aklaver.com> wrote:
On 05/23/2017 05:27 PM, Ken Tanzer wrote:
But the install still goes to 9.2:
PATH=/usr/local/pgsql96/bin/:$PATH make USE_PGXS=1 install
Did you do:
PATH=/usr/local/pgsql96/bin/:$PATH make USE_PGXS=1 clean all
I did.
Or is there some environment variable set that could be interfering?
I didn't see anything that would apply. I've attached a dump of environment variables and also a re-run of the compile/install process.
Try without the trailing:
PATH=/usr/local/pgsql96/bin:$PATH make USE_PGXS=1 clean all
Sorry, not sure I follow what is the trailing part here?
Does the compile stage specify where a module is to be installed? Or is it determined at install time?
Apart from the extra 96/bin directories I'm accumulating, I don't see anything suspicious in my path. (And my /usrl/ocal/(s)bin directories are empty.)
[root@hosting table_log-0.4.4]# PATH=/usr/local/pgsql96/bin:$PATH ; echo "Path is: $PATH" ; make USE_PGXS=1 clean all
Path is: /usr/local/pgsql96/bin:/usr/local/pgsql96/bin:/usr/local/pgsql96/bin:/usr/local/pgsql96/bin:/usr/local/pgsql96/bin:/usr/local/pgsql96/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/root/bin
rm -f table_log.so table_log.o
...
[root@hosting table_log-0.4.4]# PATH=/usr/local/pgsql96/bin:$PATH ; echo "Path is: $PATH" ; make USE_PGXS=1 install
Path is: /usr/local/pgsql96/bin:/usr/local/pgsql96/bin:/usr/local/pgsql96/bin:/usr/local/pgsql96/bin:/usr/local/pgsql96/bin:/usr/local/pgsql96/bin:/usr/local/pgsql96/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/root/bin
/bin/mkdir -p '/usr/pgsql-9.2/share/contrib'
/bin/mkdir -p '/usr/pgsql-9.2/lib'
/bin/mkdir -p '/usr/pgsql-9.2/doc/contrib'
/usr/bin/install -c -m 644 table_log.sql '/usr/pgsql-9.2/share/contrib/'
/usr/bin/install -c -m 755 table_log.so '/usr/pgsql-9.2/lib/'
/usr/bin/install -c -m 644 .//README.table_log '/usr/pgsql-9.2/doc/contrib/'
Thanks,
Ken
AGENCY Software
A Free Software data system
By and for non-profits
(253) 245-3801
learn more about AGENCY or
follow the discussion.
The biggest problem is that I was out in the Sun too long today and was not paying attention to what you posted. This part:
PATH=/usr/local/pgsql96/bin:$PATH
is from how I installed various versions of Postgres from source on my machine. My guess is it does not match your setup. You need to find where pg_config is for your 9.6 install and use that path.
Egads, my bad for not catching that path. Works fine with adding the (actually-existing) /usr/pgsql-9.6/bin to the path. Thanks so much for your help!
Can I also ask y'all a more general question about this, specifically related to how Postgres is packaged for RHEL/Centos? I've got both 9.6 and 9.2 installed. In this case though, it seems that the 9.2 version is privileged/selected by default. But psql defaults to the 9.6 version. Are there other similar things that will default to either 9.2 or 9.6? And if so, what controls that behavior, is it easily-changeable, and/or can you go back and forth?
I've never tried running two versions at once before. Maybe this is an isolated incident, but I'm just trying to get my mind around the concept, and know what kind of pitfalls if any to expect or beware of. Thanks!
Ken
AGENCY Software
A Free Software data system
By and for non-profits
(253) 245-3801
learn more about AGENCY or
follow the discussion.