Horton

Re: Draft release notes complete

Alvaro Herrera <alvherre@commandprompt.com>

View thread
From: Alvaro Herrera <alvherre@commandprompt.com>
To: Andrew Dunstan <andrew@dunslane.net>
Cc: Magnus Hagander <magnus@hagander.net>, Tom Lane <tgl@sss.pgh.pa.us>, Bruce Momjian <bruce@momjian.us>, Pg Hackers <pgsql-hackers@postgresql.org>
Date: 2012-05-10T13:05:10Z
Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Expose track_iotiming information via pg_stat_statements.

  2. Rewrite GiST support code for rangetypes.

  3. Clean up a couple of box gist helper functions.

  4. Replace the "New Linear" GiST split algorithm for boxes and points with a

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@commandprompt.com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support