From: | David Jantzen <djantzen(at)ql2(dot)com> |
---|---|
To: | "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
Subject: | Mixing DBLink versions |
Date: | 2010-03-15 21:29:51 |
Message-ID: | 78AE7A6D-1E37-4B74-BFEA-0E94BA9FA2C9@ql2.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Hi All,
Due to some historical idiosyncracies in our environment, we have a custom 8.3.7 database installation built from source. We'd like to install dblink into this, however there are some problems with doing so:
1) the 8.3.7 database was built on a CentOS 4 build box that has since gone away
2) currently we have only 8.3.9 code built against CentOS 5
3) the GCC compiler on CentOS 4 was quite old
4) possible API changes in dblink between those versions
My question, how risky would it be to copy the dblink.so and .sql files from the CentOS 5 compilation of Postgres 8.3.9 over to the CentOS 4 compilation of Postgres 8.3.7? If runtime errors result, how severe would they be? I.e., would they take down a postgres backend or possibly the postmaster daemon?
Thanks,
David
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2010-03-15 22:35:43 | Re: Autovac vs manual with analyze |
Previous Message | Thomas Kellerer | 2010-03-15 20:11:13 | Re: how to get notification in front end application when ever postgre DB table is modified, any tool, jar, api available? |