From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
Cc: | "Patches (PostgreSQL)" <pgsql-patches(at)postgresql(dot)org> |
Subject: | Re: plperl and pltcl installcheck targets |
Date: | 2005-05-11 15:46:54 |
Message-ID: | 4461.1115826414@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
Andrew Dunstan <andrew(at)dunslane(dot)net> 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 bring
> in other PLs as has been discussed, some standard might be useful.
Actually, we have a standard: it's pg_regress. The right thing for
someone to do is migrate all these tests into the form already used
for the main backend and all of contrib.
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.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2005-05-11 15:54:56 | Re: Oracle Style packages on postgres |
Previous Message | Andrew Dunstan | 2005-05-11 14:55:08 | plperl and pltcl installcheck targets |
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2005-05-11 15:47:27 | Re: [BUGS] BUG #1588: pg_autovacuum sleep parameter overflow |
Previous Message | Tom Lane | 2005-05-11 15:41:19 | Re: [BUGS] BUG #1588: pg_autovacuum sleep parameter overflow |