Re: CREATE LANGUAGE workaround

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
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 19:08:48
Message-ID: 5748.1254078528@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Martin Gainty <mgainty(at)hotmail(dot)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

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2009-09-27 19:14:24 Re: Questions On Tablespace
Previous Message Gerhard Wiesinger 2009-09-27 19:04:31 Re: PostgreSQL reads each 8k block - no larger blocks are used - even on sequential scans