pg.ddx.io pgsql-admin@postgresql.org mailing list archivehelp / color / mirror / Atom feed
From: David Jantzen <djantzen@ql2.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-admin@postgresql.org <pgsql-admin@postgresql.org>
Subject: Re: Mixing DBLink versions
Date: Mon, 15 Mar 2010 19:25:49 -0700
Message-ID: <D40579A5-A7E4-4D93-B2D0-4668DDE89F8F@ql2.com> (raw)
In-Reply-To: <26934.1268701293@sss.pgh.pa.us>
References: <78AE7A6D-1E37-4B74-BFEA-0E94BA9FA2C9@ql2.com>
<26934.1268701293@sss.pgh.pa.us>
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 <djantzen@ql2.com> writes:
>> 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?
>
> 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.
>
> 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).
>
> As for your direct question: no, I wouldn't count on that to work.
> RHEL4 and RHEL5 had different glibc versions didn't they?
>
> regards, tom lane
view thread (4+ messages) latest in thread
Message-ID: <D40579A5-A7E4-4D93-B2D0-4668DDE89F8F@ql2.com> Permalink: ../D40579A5-A7E4-4D93-B2D0-4668DDE89F8F@ql2.com/ Also on: postgresql.org/message-id/D40579A5-A7E4-4D93-B2D0-4668DDE89F8F@ql2.com ·
reply
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Reply to all the recipients from your mail client; the link fills in the headers below: reply via email Some clients, webmail especially, drop In-Reply-To and References from a link, and the reply then starts a new thread: use the mbox below. To: pgsql-admin@postgresql.org Cc: djantzen@ql2.com, tgl@sss.pgh.pa.us Subject: Re: Mixing DBLink versions In-Reply-To: <D40579A5-A7E4-4D93-B2D0-4668DDE89F8F@ql2.com> References: <78AE7A6D-1E37-4B74-BFEA-0E94BA9FA2C9@ql2.com> <26934.1268701293@sss.pgh.pa.us> <D40579A5-A7E4-4D93-B2D0-4668DDE89F8F@ql2.com> * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions for how to clone and mirror all data and code used for this inbox