Re: BUG #5642: pg_upgrade does not handle shared libraries for language handlers - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #5642: pg_upgrade does not handle shared libraries for language handlers
Date
Msg-id 21145.1283915792@sss.pgh.pa.us
Whole thread Raw
In response to Re: BUG #5642: pg_upgrade does not handle shared libraries for language handlers  ("David Platt" <davidplatt@davidplatt.com>)
Responses Re: BUG #5642: pg_upgrade does not handle shared libraries for language handlers  ("David Platt" <davidplatt@davidplatt.com>)
List pgsql-bugs
"David Platt" <davidplatt@davidplatt.com> writes:
> No, that was defined in the database through pg_dump, edit the path, the
> loading the pg_dump using psql.  For each time the database has been
> upgraded.

> We started using Postgres in 2000 and even plpgsql had to be created as a
> language back then, there was no creation by default.  Evidently the
> documentation indicated that the path to the shared library had to be
> declared because I don't remember any example showing $library.

$libdir was implemented in 2001, so you've been doing it the hard way
for awhile :-(.  However, I don't immediately find anything in the
release notes suggesting that people change to using that, so it's
definitely not all your fault.

            regards, tom lane

pgsql-bugs by date:

Previous
From: "David Platt"
Date:
Subject: Re: BUG #5642: pg_upgrade does not handle shared libraries for language handlers
Next
From: "David Platt"
Date:
Subject: Re: BUG #5642: pg_upgrade does not handle shared libraries for language handlers