EnterpriseDB / mongo_fdw

PostgreSQL foreign data wrapper for MongoDB
GNU Lesser General Public License v3.0
330 stars 70 forks source link

Ubuntu 14.04 - no joy #47

Open dwalbeck opened 8 years ago

dwalbeck commented 8 years ago

Tried to get this installed on 3 of our DB servers, all of which are running Ubuntu 14.04 and upgraded PostgreSQL to 9.5. Had the same issue on all 3 servers, where the autogen.sh ran fine, but only seemed to compile the json-c and mongo-c-driver. Tried using both types, --with-master and --with-legacy, both of which worked the same. Tried installing the FDW using "make -f Makefile.meta && make -f Makefile.meta install", which would fail consistently with the following error:

/usr/bin/ld: json-c/json_util.o: relocation R_X86_64_32 against `.rodata.str1.8' can not be used when making a shared object; recompile with -fPIC json-c/json_util.o: error adding symbols: Bad value collect2: error: ld returned 1 exit status make: *\ [mongo_fdw.so] Error 1

I could get it to install if I ran a "make clean && make && make install", which compiled the wrapper and installed it. When I use it, it loads the extension and allows the creation of a server and mapped user, which I also grant rights to that user to use. Any query however takes a bit to run and always returns an empty set. Tried simplifying the foreign table down to just two columns, the _id and a label field (varchar), but get the same results. Could be due to way the wrapper was compiled, but couldn't get it to install any other way. Any ideas?

acheccuc commented 8 years ago

I am experiencing the same behaviour on RHEL7

ahsanhadi commented 8 years ago

The support for PG 9.5 was added in Dec 2015 so it should work fine with PG 9.5. The problem may be building the FDW or dependent libraries on the said platform. We can try installing and testing this on RHEL 7 or Ubuntu 14.04 with PG 9.5. However i need to prioritise this with your product management...

andreasscherbaum commented 5 years ago

Ubuntu 14.04 LTS is running out of support this April. Are you still on this version? Is the issue still present?

vaibhavdalvi93 commented 2 years ago

@dwalbeck , Are you still facing this issue?