| From: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: New regression test time |
| Date: | 2013-07-02 15:28:15 |
| Message-ID: | alpine.DEB.2.02.1307021723240.31305@localhost6.localdomain6 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> What is more, it's entirely possibly to invoke pg_regress with multiple
> --schedule arguments, so we could, for example, have a makefile target
> that would run both the check and some other schedule of longer running
> tests.
I missed this fact, because I've not seen any example of multiple schedule
option in regress, so in the split test POC I concatenated files for the
same purpose, but multiple schedule options looks like a much better
alternative.
--
Fabien.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2013-07-02 15:36:38 | Re: Randomisation for ensuring nlogn complexity in quicksort |
| Previous Message | Andres Freund | 2013-07-02 15:24:00 | Re: MVCC catalog access |