Pivotal Knowledge Base

Follow

What needs to be done after upgrading GPDB

Symptom:

After GPDB upgrade, GPText functions error out as below:

hold1=# select gptext.version();
ERROR:  could not access file "gptext-1.1.0.1": No such file or directory

Root cause:

There are 2 soft links in old $GPHOME pointing to libraries in $GPTXTHOME.
After GPDB upgrade, the 2 soft links are missing and need to be recreated manually.
Note that, gppkg can not fix this.
The 2 soft links are (Take GPText 1.1.0.1 for example):

/usr/local/greenplum-db/lib/postgresql/gptext-1.1.0.1.so -> /usr/local/greenplum-text-1.1.0.1/lib/gptext-gpdb42-1.1.0.1.so
/usr/local/greenplum-db/lib/python/gptextlib -> /usr/local/greenplum-text-1.1.0.1/lib/python/gptextlib

Affected Version:
GPText 1.1.x.x, 1.2.x.x

Solution:
After GPDB upgrade, when GPDB is down, manually create the 2 soft links on all servers using "gpssh".

Take GPText 1.1.0.1 for example:

gpssh -f all_hosts
cd /usr/local/greenplum-db/lib/postgresql
ln -s /usr/local/greenplum-text-1.1.0.1/lib/gptext-gpdb42-1.1.0.1.so gptext-1.1.0.1.so 
cd /usr/local/greenplum-db/lib/python
ln -s /usr/local/greenplum-text-1.1.0.1/lib/python/gptextlib gptextlib

Take GPText 1.2.0.0 for example:

gpssh -f all_hosts
cd /usr/local/greenplum-db/lib/postgresql
ln -s /usr/local/greenplum-text-1.2.0.0/lib/gptext-gpdb42-1.2.0.0.sogptext-1.2.0.0.so
cd /usr/local/greenplum-db/lib/python
ln -s /usr/local/greenplum-text-1.2.0.0/lib/python/gptextlib gptextlib

Take GPText 1.2.2.0 or above for example:
We have a new feature to use gptext_migrator to create the link automatically:

gptext-migrator -s


Comments

Powered by Zendesk