creating languages in the pg_catalog schema? - Mailing list pgsql-general

From Jochem van Dieten
Subject creating languages in the pg_catalog schema?
Date
Msg-id 3E084D94.3010200@oli.tudelft.nl
Whole thread Raw
Responses Re: creating languages in the pg_catalog schema?  (Tom Lane <tgl@sss.pgh.pa.us>)
List 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


pgsql-general by date:

Previous
From: "Jefim Matskin"
Date:
Subject: FW: BUG in trigger and foreign keys
Next
From:
Date:
Subject: Re: server closed the connectio unexpectedly