From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Oberpriller, Wade D(dot)" <oberpwd(at)nsc-msg01(dot)network(dot)com> |
Cc: | "PostgreSQL General Help (E-mail)" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Creating languages with relative path to shared libraries |
Date: | 2001-11-12 17:33:42 |
Message-ID: | 15784.1005586422@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
"Oberpriller, Wade D." <oberpwd(at)nsc-msg01(dot)network(dot)com> writes:
> When I do a
> createlang -L $MYDIR plpgsql template1
> It appears that MYDIR must be an absolute path to a directory containing
> plpgsql.so. I am wondering if there is any way to make it work with a
> relative path (like ../lib). I am trying to build a database on a
> development machine and then copy it on to a production machine. The paths
> where it is built are differenct than where it will reside and I am running
> into dynamic linking issues. Any ideas?
FWIW, this is solved in 7.2 by building a search path into the backend
itself. createlang now enters the shlib path as just
$libdir/plpgsql
so that the function definition isn't dependent on installation path.
May not help you much today though :-(
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Frank Bax | 2001-11-12 17:51:21 | 7.0.2 -> 7.1 performance drop |
Previous Message | Helge Bahmann | 2001-11-12 17:26:31 | Re: psql -f backup.out || file too big - SOLVED |