Received: from maia.hub.org (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id 98D9665A8D1 for ; Mon, 15 Mar 2010 23:26:04 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 81148-01 for ; Tue, 16 Mar 2010 02:25:53 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from ql2.com (spite.ql2.com [66.150.167.51]) by mail.postgresql.org (Postfix) with ESMTP id D661C65A8C5 for ; Mon, 15 Mar 2010 23:25:53 -0300 (ADT) Received: from ex01.corp.ql2.com (fear10.ql2.com [192.168.20.19]) by mailhub01.ql2.com (Postfix) with ESMTP id E89EC10186; Mon, 15 Mar 2010 19:25:50 -0700 (PDT) Received: from ex01.corp.ql2.com ([192.168.20.19]) by ex01.corp.ql2.com ([192.168.20.19]) with mapi; Mon, 15 Mar 2010 19:25:50 -0700 From: David Jantzen To: Tom Lane CC: "pgsql-admin@postgresql.org" Date: Mon, 15 Mar 2010 19:25:49 -0700 Subject: Re: Mixing DBLink versions Thread-Topic: [ADMIN] Mixing DBLink versions Thread-Index: AcrEr/4aXXOF4vBMTserPsxQYjdWrw== Message-ID: References: <78AE7A6D-1E37-4B74-BFEA-0E94BA9FA2C9@ql2.com> <26934.1268701293@sss.pgh.pa.us> In-Reply-To: <26934.1268701293@sss.pgh.pa.us> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-2.599 tagged_above=-10 required=5 tests=BAYES_00=-2.599 X-Spam-Level: X-Archive-Number: 201003/106 X-Sequence-Number: 33905 Thanks for the detailed response. We'll look at upgrading to 8.3.9 from an= RPM. On Mar 15, 2010, at 6:01 PM, Tom Lane wrote: > David Jantzen writes: >> Due to some historical idiosyncracies in our environment, we have a cust= om 8.3.7 database installation built from source. We'd like to install dbl= ink into this, however there are some problems with doing so: >=20 >> 1) the 8.3.7 database was built on a CentOS 4 build box that has since g= one 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 >=20 >> 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 compil= ation of Postgres 8.3.7? If runtime errors result, how severe would they b= e? I.e., would they take down a postgres backend or possibly the postmaste= r daemon?=20 >=20 > I think you've got a fundamental problem that you'd better fix. If you > are unable to rebuild the database from source then you are unable to > update --- and you are already three minor versions behind and missing > multiple security and crash-risk bug fixes. You're living on borrowed > time, and NEED to reinstantiate your ability to build for that platform. > Or move to a newer one. >=20 > FWIW, you could probably get back a RHEL4 build environment pretty > cheaply by setting up a suitable "mock" chroot on a recent Fedora > version (installed on the same type of hardware). >=20 > As for your direct question: no, I wouldn't count on that to work. > RHEL4 and RHEL5 had different glibc versions didn't they? >=20 > regards, tom lane