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 <alvhe...@commandprompt.com> The PostgreSQL Company - Command Prompt, Inc. PostgreSQL Replication, Consulting, Custom Development, 24x7 support -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
