Horton

Re: Draft release notes complete

Andrew Dunstan <andrew@dunslane.net>

View thread
From: Andrew Dunstan <andrew@dunslane.net>
To: Stephen Frost <sfrost@snowman.net>
Cc: Bruce Momjian <bruce@momjian.us>, Alvaro Herrera <alvherre@2ndquadrant.com>, 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-06T03:33:35Z
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/05/2012 11:01 PM, Stephen Frost wrote:
> * Andrew Dunstan (andrew@dunslane.net) wrote:
>> The buildfarm code does not run if there are no changes. The job
>> runs, sees that there are no changes, and exits.
> Right, hence it makes great sense to use it for this (as opposed to
> Bruce's previous script or some other new one).  While it might appear
> to be overkill, it actually does lots of useful and good things and
> integrates better with the existing setup anyway.
>
> Now that you've provided the magic sauce wrt --skip-steps, can we get an
> admin to implement a doc-only build that runs more frequently to update
> the dev docs..?
>
> Andrew, if we're going to rely on that, even just internally, perhaps we
> should go ahead and add documentation for it?
>
> 	


You mean in my copious spare time?

AIUI the only thing stopping the admins from doing what is wanted is a 
shortage of tuits. I suspect if we're all a tiny bit patient it will happen.

But I guess they can speak for themselves.

cheers

andrew