> > Will I destroy things if I execute
> > update pg_proc set probin = '/usr/lib/pgsql/plpgsql.so' where proname =
> > 'plpgsql_call_handler';
>
> Nope ... that's what I'd probably do. You could alternatively use
> CREATE OR REPLACE FUNCTION if you wanted to be pure, but I'd say that
> that c
Christopher Kings-Lynne <[EMAIL PROTECTED]> writes:
>>> Will I destroy things if I execute
>>> update pg_proc set probin = '/usr/lib/pgsql/plpgsql.so' where proname =
>>> 'plpgsql_call_handler';
>>
>> Nope ... that's what I'd probably do.
> Even better change it to '$libdir/plpgsql.so'.
Good po
On Sat, Jun 28, 2003 at 01:25:12AM -0400, Tom Lane wrote:
> Christopher Kings-Lynne <[EMAIL PROTECTED]> writes:
> >>> Will I destroy things if I execute
> >>> update pg_proc set probin = '/usr/lib/pgsql/plpgsql.so' where proname =
> >>> 'plpgsql_call_handler';
> >>
> >> Nope ... that's what I'd p
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
Adam Haberlach <[EMAIL PROTECTED]> writes:
> Will I destroy things if I execute
> update pg_proc set probin = '/usr/lib/pgsql/plpgsql.so' where proname =
> 'plpgsql_call_handler';
Nope ... that's what I'd probably do. You could alternatively use
CREATE OR REPLACE FUNCTION if you wanted to
