| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Magnus Hagander <magnus(at)hagander(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Bruce Momjian <bruce(at)momjian(dot)us>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Draft release notes complete |
| Date: | 2012-05-10 13:05:10 |
| Message-ID: | 1336655010-sup-6744@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Excerpts from Andrew Dunstan's message of jue may 10 07:19:53 -0400 2012:
> BTW, if there has been no change a buildfarm animal normally does no
> work (other than a git pull followed by the check for updates), which is
> why it's often safe to schedule it very frequently. However, if you need
> to schedule tasks at times when it's known not to be running then a
> sparse schedule makes sense.
Magnus was trying to say that the physical machine has other VMs doing
unrelated stuff, not that the BF animal VM itself had other things to
do.
--
Álvaro Herrera <alvherre(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2012-05-10 13:12:57 | Re: Draft release notes complete |
| Previous Message | Magnus Hagander | 2012-05-10 13:04:21 | Re: incorrect handling of the timeout in pg_receivexlog |