Обсуждение: oracle_fdw Question
Hi,
I am trying to install and configure the oracle_fdw on PostgreSQL DB servers.
What we are trying is, inorder to install (make, make install) oracle_fdw on all DB servers,we want to compile on one server and want build a package/tar file to copy the library files and required SQL scripts into all other servers.
So that it will reduce the installation efforts.
can we copy the oracle_fdw.so file into "<directory>/9.5/lib/postgresql"
And oracle_fdw.control,oracle_fdw--1.1.sql and oracle_fdw--1.0--1.1.sql files into "<directory>/9.5/share/postgresql/extension" directory.
Is this the right approach?
Is there any process to create re-locatable binary files for oracle_fdw?
Thanks,
chiru
On Tue, 13 Feb 2018 at 5:55 am, chiru r <chirupg@gmail.com> wrote:
Hi,I am trying to install and configure the oracle_fdw on PostgreSQL DB servers.What we are trying is, inorder to install (make, make install) oracle_fdw on all DB servers,we want to compile on one server and want build a package/tar file to copy the library files and required SQL scripts into all other servers.So that it will reduce the installation efforts.can we copy the oracle_fdw.so file into "<directory>/9.5/lib/postgresql"And oracle_fdw.control,oracle_fdw--1.1.sql and oracle_fdw--1.0--1.1.sql files into "<directory>/9.5/share/postgresql/extension" directory.Is this the right approach?Is there any process to create re-locatable binary files for oracle_fdw?
If you are installing same Postgres versions across all the DB servers, then, I would suggest build re-locatable Postgres binaries which includes oracle_fdw as well.
Thanks,
Venkata B
Thanks,chiru
--
Venkata B N
Database Consultant
chiru r wrote: > I am trying to install and configure the oracle_fdw on PostgreSQL DB servers. > What we are trying is, inorder to install (make, make install) oracle_fdw on all DB servers,we want to compile on one serverand want build a package/tar file to copy the library files and required SQL scripts into all other servers. > So that it will reduce the installation efforts. > > can we copy the oracle_fdw.so file into "<directory>/9.5/lib/postgresql" > And oracle_fdw.control,oracle_fdw--1.1.sql and oracle_fdw--1.0--1.1.sql files into "<directory>/9.5/share/postgresql/extension"directory. > Is this the right approach? > > Is there any process to create re-locatable binary files for oracle_fdw? As long as you have the same version of the same operating system on all machines and all required software is installed in the same versions, it should be no problem to build it on one machine and install it on the others. The process you describe looks right; just make sure the files end up in the same directories where "make install" installs them on the build machine. I am not quite sure what you mean with a "relocatable binary file". Yours, Laurenz Albe
Thank you.
On Tue, Feb 13, 2018 at 3:31 AM, Laurenz Albe <laurenz.albe@cybertec.at> wrote:
chiru r wrote:
> I am trying to install and configure the oracle_fdw on PostgreSQL DB servers.
> What we are trying is, inorder to install (make, make install) oracle_fdw on all DB servers,we want to compile on one server and want build a package/tar file to copy the library files and required SQL scripts into all other servers.
> So that it will reduce the installation efforts.
>
> can we copy the oracle_fdw.so file into "<directory>/9.5/lib/postgresql"
> And oracle_fdw.control,oracle_fdw--1.1.sql and oracle_fdw--1.0--1.1.sql files into "<directory>/9.5/share/ postgresql/extension" directory.
> Is this the right approach?
>
> Is there any process to create re-locatable binary files for oracle_fdw?
As long as you have the same version of the same operating system on
all machines and all required software is installed in the same versions,
it should be no problem to build it on one machine and install it on the others.
The process you describe looks right; just make sure the files end up in the
same directories where "make install" installs them on the build machine.
I am not quite sure what you mean with a "relocatable binary file".
Yours,
Laurenz Albe