Skip site navigation (1) Skip section navigation (2)

Re: BUG #5642: pg_upgrade does not handle shared libraries for language handlers

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "David Platt" <davidplatt(at)davidplatt(dot)com>
Cc: "'Bruce Momjian'" <bruce(at)momjian(dot)us>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #5642: pg_upgrade does not handle shared libraries for language handlers
Date: 2010-09-08 03:16:32
Message-ID: 21145.1283915792@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-bugs
"David Platt" <davidplatt(at)davidplatt(dot)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

In response to

Responses

pgsql-bugs by date

Next:From: David PlattDate: 2010-09-08 03:24:13
Subject: Re: BUG #5642: pg_upgrade does not handle shared libraries for language handlers
Previous:From: David PlattDate: 2010-09-08 02:58:23
Subject: Re: BUG #5642: pg_upgrade does not handle shared libraries for language handlers

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group