Re: CREATE LANGUAGE workaround - Mailing list pgsql-general

From Tom Lane
Subject Re: CREATE LANGUAGE workaround
Date
Msg-id 5748.1254078528@sss.pgh.pa.us
Whole thread Raw
In response to CREATE LANGUAGE workaround  (Martin Gainty <mgainty@hotmail.com>)
List pgsql-general
Martin Gainty <mgainty@hotmail.com> writes:
> 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?

I'm not sure what you are trying to accomplish, but the above looks like
it should all just be replaced by
    CREATE LANGUAGE plpgsql;
in reasonably modern versions of Postgres.

There is no such thing as a "plpgsql type".

            regards, tom lane

pgsql-general by date:

Previous
From: Gerhard Wiesinger
Date:
Subject: Re: PostgreSQL reads each 8k block - no larger blocks are used - even on sequential scans
Next
From: Tom Lane
Date:
Subject: Re: Questions On Tablespace