Re: Manual fixing of plpgsql_call_handler binary location -- good idea? - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Manual fixing of plpgsql_call_handler binary location -- good idea?
Date
Msg-id 14377.1056759672@sss.pgh.pa.us
Whole thread Raw
In response to Manual fixing of plpgsql_call_handler binary location -- good idea?  (Adam Haberlach <adam@newsnipple.com>)
Responses Re: Manual fixing of plpgsql_call_handler binary location  (Christopher Kings-Lynne <chriskl@familyhealth.com.au>)
List pgsql-hackers
Adam Haberlach <adam@newsnipple.com> 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 be pure, but I'd say that
that creates as many opportunities to make mistakes as it removes, since
you'd have to be careful to get all the other attributes right too.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Possible mistake in new array syntax
Next
From: Ron Johnson
Date:
Subject: Re: [GENERAL] Physical Database Configuration