Re: [PATCHES] plperl and pltcl installcheck targets - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [PATCHES] plperl and pltcl installcheck targets
Date
Msg-id 13727.1115836358@sss.pgh.pa.us
Whole thread Raw
In response to Re: [PATCHES] plperl and pltcl installcheck targets  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: [PATCHES] plperl and pltcl installcheck targets  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers
Andrew Dunstan <andrew@dunslane.net> writes:
> Tom Lane wrote:
>> I think this would require a small addition to the pg_regress script
>> to make it configurable as to which PL to install, instead of always
>> installing plpgsql, but that seems like a reasonable thing to do.

> I'm not sure why it would matter having it there. I would just make the 
> first test to load the language in question - pretty much this, right?

> CREATE FUNCTION "plperl_call_handler" () RETURNS language_handler AS 
> '$libdir/plperl' LANGUAGE C;
> CREATE TRUSTED LANGUAGE "plperl" HANDLER "plperl_call_handler";
> CREATE LANGUAGE "plperlu" HANDLER "plperl_call_handler";

The point is that I'd rather test createlang than duplicate it.

(In the back of my mind also is that running createlang is a waste of
time for the contrib tests, and so it'd be nice if pg_regress didn't
load any PL unless told to.)
        regards, tom lane


pgsql-hackers by date:

Previous
From: "Dave Held"
Date:
Subject: Re: Oracle Style packages on postgres
Next
From: Tom Lane
Date:
Subject: Re: Oracle Style packages on postgres