Re: CREATE LANGUAGE workaround

From: Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>
To: Martin Gainty <mgainty(at)hotmail(dot)com>
Cc: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: CREATE LANGUAGE workaround
Date: 2009-09-27 18:34:29
Message-ID: dcc563d10909271134x96169abrfd9d8850a6b8406f@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

2009/9/27 Martin Gainty <mgainty(at)hotmail(dot)com>:
> I am slowly transferring my Procedures over and came upon this workaround
> implemented by a script which maps the plpgsql (type) to call plpgsql.dll
> pg_finfo_plpgsql_call_handler
>
> # Create a plpgsql handler for plpgsql type
> CREATE FUNCTION pg_finfo_plpgsql_call_handler() RETURNS plpgsql AS
> '/postgres/pgsql/bin/plpgsql.dll' LANGUAGE C;
> CREATE TRUSTED PROCEDURAL LANGUAGE plpgsql HANDLER
> pg_finfo_plpgsql_call_handler;
>
> is there a system defined script I can run which would map the plpgsql
> handler to the plpgsql type automatically?

On Unix there's a createlang command (run from the CLI, not from psql)
that does this.

createlang plpgsql dbname

In response to

Browse pgsql-general by date

  From Date Subject
Next Message InterRob 2009-09-27 18:45:19 Re: generic modelling of data models; enforcing constraints dynamically...
Previous Message Carlo Camerino 2009-09-27 18:27:59 Questions On Tablespace