Re: [HACKERS] [PATCHES] plperl and pltcl installcheck targets

2005-05-11 Thread Tom Lane
Andrew Dunstan <[EMAIL PROTECTED]> writes: > Aha. ok. should be fairly trivial. I'm thinking of something like >--load-languages=lang1,lang2,lang3 > (in case we ever want more than one). Might be a little easier as multiple switches: --load-language=lang1 --load-language=lang2

Re: [HACKERS] [PATCHES] plperl and pltcl installcheck targets

2005-05-11 Thread Andrew Dunstan
Tom Lane wrote: 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.) Aha. ok. should be fairly trivial. I'm thinkin

Re: [HACKERS] [PATCHES] plperl and pltcl installcheck targets

2005-05-11 Thread Tom Lane
Andrew Dunstan <[EMAIL PROTECTED]> 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 wo

Re: [HACKERS] [PATCHES] plperl and pltcl installcheck targets

2005-05-11 Thread Andrew Dunstan
[redirected to -hackers] Tom Lane wrote: Andrew Dunstan <[EMAIL PROTECTED]> writes: Is it worth rearranging things for plpython so that it follows the same test layout as the other 2 (i.e. a test subdir with all the test files and a script called runtest that does the work)? Especially if we b