Re: pg_restore error

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Laurette Cisneros <laurette(at)nextbus(dot)com>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: pg_restore error
Date: 2002-09-03 22:27:24
Message-ID: 21045.1031092044@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Laurette Cisneros <laurette(at)nextbus(dot)com> writes:
> I am currently on 7.2.1 and the software location has changed (to
> /usr/local/pgsql). And, further research shows that the pg_proc shows:
> This shows /usr/local/pgsql-7.2/lib/plpgsql for the "probin" column.

> How should an update of software be handled as per pg_proc?

The preferred contents of probin are now like
$libdir/plpgsql
(the dollar sign is literal text here). As of 7.2 the server will
substitute a suitable directory name for "$libdir". You probably
have a database that was reloaded from an old dump without taking
advantage of this feature --- before 7.2 you could only use an
absolute path in probin. Now, absolute paths are deprecated for exactly
the reason that they make version updates hard.

Note the lack of a ".so" in that probin entry, too. This is also
a recommended new practice in 7.2 --- no reason to put
platform-dependent assumptions about shared library extensions into
your dumps.

regards, tom lane

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Laurette Cisneros 2002-09-03 22:32:28 [GWAVA:ecwa6lyk] Source block message notification (fwd)
Previous Message Laurette Cisneros 2002-09-03 22:13:51 pg_restore error