From: | Adam Witney <awitney(at)sghms(dot)ac(dot)uk> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Beta2 - A Late Announcement |
Date: | 2002-09-30 15:08:29 |
Message-ID: | B9BE277D.8987%a.witney@sghms.ac.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-announce pgsql-general |
On 30/9/02 3:57 pm, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Adam Witney <awitney(at)sghms(dot)ac(dot)uk> writes:
>> Ahh yes, it is failing just as it is trying to create the
>> plpgsql_call_handler ready for adding the PL/pgSQL language, which includes
>> a hard coded path to plpgsql.so
>
>> If I manually changed the path to the newly complied plpgsql.so would that
>> be ok?
>
> I'd recommend editing the dump to use path
> '$libdir/plpgsql'
> which is the preferred setup going forward --- it's
> installation-independent because the backend will automatically add
> the correct library-directory path and shared-library extension.
>
> createlang has created languages this way since 7.2, but dumps loaded
> from prior releases probably still have hardcoded paths in them :-(
Yup, I just manually changed the path to the language library and those
errors disappeared.
This was dumped from 7.2.2 but the paths were hardcoded.
Thanks for your help
Adam
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2002-10-01 05:15:10 | OS X loader failure (was Re: Beta2 - A Late Announcement) |
Previous Message | Tom Lane | 2002-09-30 14:57:00 | Re: Beta2 - A Late Announcement |
From | Date | Subject | |
---|---|---|---|
Next Message | Greg Copeland | 2002-09-30 15:10:09 | Re: [HACKERS] current_timestamp after queries |
Previous Message | Bruce Momjian | 2002-09-30 15:08:02 | Re: LIMIT: does it cause the query to find all matching sets |