| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, "Patches (PostgreSQL)" <pgsql-patches(at)postgresql(dot)org> |
| Subject: | Re: [HACKERS] plperl and pltcl installcheck targets |
| Date: | 2005-05-14 19:46:19 |
| Message-ID: | 5406.1116099979@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:
> I agree. That will also mean that buildfarm members will automatically
> start doing the checks (as long as they are set up to build the PLs), so
> it would be an extra bonus for me :-)
The only argument I can think of against it is that the buildfarm
status page will then not distinguish core system check failures
from PL check failures. If that doesn't bother you, we can make
it so.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2005-05-14 21:14:14 | Re: [HACKERS] plperl and pltcl installcheck targets |
| Previous Message | Andrew Dunstan | 2005-05-14 18:53:56 | Re: [HACKERS] plperl and pltcl installcheck targets |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2005-05-14 20:55:01 | Re: Exec statement logging |
| Previous Message | Andrew Dunstan | 2005-05-14 18:53:56 | Re: [HACKERS] plperl and pltcl installcheck targets |