Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id B1781476074 for ; Tue, 3 Sep 2002 18:27:40 -0400 (EDT) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by postgresql.org (Postfix) with ESMTP id 1C1B3475F10 for ; Tue, 3 Sep 2002 18:27:40 -0400 (EDT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.5/8.12.5) with ESMTP id g83MRPZM021046; Tue, 3 Sep 2002 18:27:25 -0400 (EDT) To: Laurette Cisneros Cc: pgsql-admin@postgresql.org Subject: Re: pg_restore error In-reply-to: References: Comments: In-reply-to Laurette Cisneros message dated "Tue, 03 Sep 2002 15:13:51 -0700" Date: Tue, 03 Sep 2002 18:27:24 -0400 Message-ID: <21045.1031092044@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200209/28 X-Sequence-Number: 5567 Laurette Cisneros 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