| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Simon Riggs <simon(at)2ndquadrant(dot)com>, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Simplifying wal_sync_method |
| Date: | 2005-08-09 00:22:20 |
| Message-ID: | 42F7F73C.6010202@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane wrote:
>Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
>
>
>>So the short answer is possibly "You build the tests and we'll run 'em."
>>
>>
>
>The availability of the buildfarm certainly makes it a lot more feasible
>to do performance tests on a variety of platforms. So, who wants to
>knock something together?
>
>I suppose we would usually be interested in one-time tests, rather than
>something repeated every time CVS is touched. How might that sort of
>requirement fit into the buildfarm software design?
>
>
>
>
I'll give it some thought. Maybe a unique name would do the trick.
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2005-08-09 00:29:34 | Re: Simplifying wal_sync_method |
| Previous Message | Kris Jurka | 2005-08-09 00:15:49 | Re: Simplifying wal_sync_method |