From: | Adam Haberlach <adam(at)newsnipple(dot)com> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Manual fixing of plpgsql_call_handler binary location -- good idea? |
Date: | 2003-06-27 21:07:47 |
Message-ID: | 20030627140747.A20869@newsnipple.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
I know that we're all in end-of-release hurry, but I've got a quick
question.
We've got some machines that had postgres installed in /usr/local/pgsql
and we are moving their data directories, wholesale, onto machines with
postgres in the standard RedHat locations. This works just fine except
for the hardcoded-ness of the plpgsql_call_handler having been
previously set to /usr/local/pgsql/lib/plpgsql.so
Will I destroy things if I execute
update pg_proc set probin = '/usr/lib/pgsql/plpgsql.so' where proname = 'plpgsql_call_handler';
On the machines? This seems to work, but I wanted to see if anyone
out there wanted to tell me about this being a really stupid idea.
--
Adam Haberlach | "When your product is stolen by thieves, you
adam(at)mediariffic(dot)com | have a police problem. When it is stolen by
http://mediariffic.com | millions of honest customers, you have a
| marketing problem." - George Gilder
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2003-06-27 21:47:59 | Re: Two weeks to feature freeze |
Previous Message | Rod Taylor | 2003-06-27 20:43:30 | Re: 7.2 to 7.4 upgrade issues |