creating languages in the pg_catalog schema?

From: Jochem van Dieten <jochemd(at)oli(dot)tudelft(dot)nl>
To: pgsql-general(at)postgresql(dot)org
Subject: creating languages in the pg_catalog schema?
Date: 2002-12-24 12:05:40
Message-ID: 3E084D94.3010200@oli.tudelft.nl
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Just wondering if there are any downsides to creating a procedural
language in the pg_catalog schema instead of some other default schema.
I want the language to be available forever, regardless of schema drops
etc., to every user of the database, in every schema. And since I have
the impression that PostgreSQL (secretly) adds the pg_catalog schema to
the searchpath, it appears to be the obvious place to create the language.

Using the code below it appears to work, but are there any downsides?

CREATE FUNCTION pg_catalog.plpgsql_call_handler () RETURNS OPAQUE AS
'$libdir/plpgsql' LANGUAGE C;
CREATE TRUSTED PROCEDURAL LANGUAGE plpgsql
HANDLER pg_catalog.plpgsql_call_handler;

Best wishes,

Jochem

Responses

Browse pgsql-general by date

  From Date Subject
Next Message zurron 2002-12-24 12:09:43 Re: server closed the connectio unexpectedly
Previous Message Jefim Matskin 2002-12-24 10:40:42 FW: BUG in trigger and foreign keys