Re: Draft release notes complete

Andrew Dunstan <andrew@dunslane.net>

From: Andrew Dunstan <andrew@dunslane.net>
To: Stephen Frost <sfrost@snowman.net>
Cc: Alvaro Herrera <alvherre@2ndquadrant.com>, Bruce Momjian <bruce@momjian.us>, Tom Lane <tgl@sss.pgh.pa.us>, Peter Eisentraut <peter_e@gmx.net>, Magnus Hagander <magnus@hagander.net>, Pg Hackers <pgsql-hackers@postgresql.org>
Date: 2012-09-23T20:27:31Z
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

On 09/22/2012 01:57 PM, Stephen Frost wrote:
> Andrew,
>
>    Below is the patch that I mentioned at pgOpen.  I'm pretty sure my
>    silly github pull request got screwed up anyway, so probably best to
>    ignore it.  Regardless, please let me know what you think.  I'd be
>    happy to rework it to operate off of a single hash, though I think
>    that would require having 'one true hash' of all possible steps and
>    it kind of looked like you were trying to avoid that.



I'm not sure it's a great advance, but I'll take a look. In any case 
please sent it as a proper MIME attachment. It did not come through 
clean. Alternatively, and probably better, put this on a topic branch 
that I can git-fetch (that's recommended practice for github pull 
requests too).

cheers

andrew